Re: Assemply and using Activator.CreateInstance

Unloading assemblies from an AppDomain is a pain and not (IIRC)
recommended; any specific reason you want to do it? The other thing to
try is loading it in a separate AppDomain that you can trash
afterwards.

Marc

.

Relevant Pages

  • Re: AppDomain and Unload
    ... then the download needs to overwrite the DLL. ... Would you mind explainging what you mean by 'loading assembly into the ... > default appdomain, not the remote appdomain that you just created. ... > need to create a class that will proxy the loading/unloading of assemblies ...
    (microsoft.public.dotnet.languages.csharp)
  • Appdomain loading question
    ... I'm trying to load an assembly into a temporary AppDomain rather than ... 'AppDomainTest.exe': Loaded 'c:\visual studio ... Which clearly means it's loading into both assemblies, ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: call .net 2.0 assemblies from .net 1.1
    ... It does not stand to reason. ... 'solution' of using a new appdomain is also dodgy since all appdomains ... share the same managed heap. ... Cowboy's suggestion is best - put the .NET code ...
    (microsoft.public.dotnet.framework)
  • Re: dll loading
    ... there all loading into the ... i need it loaded in the secondary Domain ... LoadFrom loads into the _current_ AppDomain. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Assembly.Load unload separate AppDomain problem
    ... > you are returning a reference to it in the default appdomain, ... > LoadAssemblythat does the actual loading. ... >> When trying to delete the DLL file I get an exception that access is ...
    (microsoft.public.dotnet.languages.csharp)