RE: ASP.Net 1.1 shadow copy + reflection problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Joco (Joco_at_discussions.microsoft.com)
Date: 11/29/04 

Date: Mon, 29 Nov 2004 04:21:01 -0800

ic.

Well if you use strong naming (SN) the problem will not dissapear but rather
escalate. The thing is (IMHO) that then some portions of your application
would use the old code and others the new one. If that is OK with, great.

If not: I would suggest placing file watchers on the dll's and reloading
them or even restarting whole application when one of them changes.

If you load all your dll's from the same folder you can simplify this by
adding a watcher to the folder and restart/reload each time contents of the
folder change. Hope this helps somewhat.

Joco

"icesoftware" wrote:

> > What I would like to know is why do you use SC? .NET by itself does not lock
> > dll's so you should be free to change/delete/add them even when the
> > application is running.
>
> First of all thanks a lot for the hint.
> To answer your question, I use SC explicitly since I need to load libraries
> (assemblies) from other directories that are not the bin. If I was using just
> the bin then SC would be on by default and the binaries would not be locked.
> In my case, instead, through reflection I can load the assembly but it's
> locked. I needed to be able to update the binaries and so I activated the SC
> on the directories I need to load from.
>
> Now I am experimenting strong naming the assemblies since I read that if you
> do so the LoadFrom should be able to differenciate between two different
> versions of the assembly loaded from the same dir. So far I'm not getting any
> good response.
>
> Anyone has some other hint?
>
> Thanks in advance for any help.
>
> ACL

Relevant Pages

  • Re: App Domain
    ... > It's possible to load into app domain assemblies from two different ... The config file allows you to load a specific version of an assembly ... design of .NET is to have private assemblies in the application folder ... Loading from a remote site means that you download the assembly once - ...
    (microsoft.public.dotnet.framework)
  • Re: Make a DLL in C# for FoxPro
    ... Interop from managed -> COM is a different story, here we are talking about new developments, and here you have probably accepted the larger memory footprint :-) ... The first is handled by the DLL/C++ code I posted which loads the .NET runtime and allows loading of assemblies and types. ... If you're not adverse to registering components you can completely skip this step and just use the .NET wrapper component from FoxPro with CreateObject. ... *** Load Static Method ...
    (microsoft.public.dotnet.languages.csharp)
  • RE: bizarre asp.net app loading failure
    ... I gave it a try but unfortunately the fusion logs didn't show ... I see a bunch of assembly load logs for application 3e70de80 ... (presumably the name for the app pool). ... of assemblies that reference it, even though they are not used by all the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Force Load DLL From Different Dir?
    ... try load the version MyAddIn bound to at compile time. ... Actually this is NOT version related, but context related: Assemblies can ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.framework)
  • RE: some other problems
    ... | What you said is reasonable, but how can IE load the assembly ... you try to load the same page in your customized browser the assembly is ... First off the only browser that should be able to load assemblies is ... | mscorlib.resources twice, one is successful, the other is not. ...
    (microsoft.public.dotnet.vjsharp)