R Roman May 18, 2004 #1 The AppDomain.Unload doesn't seem to be releasing a lock on a 'dll' assembly file dynamically loaded into the application domain. Why?
The AppDomain.Unload doesn't seem to be releasing a lock on a 'dll' assembly file dynamically loaded into the application domain. Why?
G Guest May 19, 2004 #2 Are you sure that the assemblies are not loaded into the main AppDomain as well Regards, Jakob.
D David Levine May 20, 2004 #3 A very common mistake is to create an appdomain, and then execute something like Assembly a = myAppDomain.Load("someAsm.dll"); this has the effect of loading the assembly in both appdomains. This link has some examples of how to do what you want. http://www.gotdotnet.com/team/clr/AppdomainFAQ.aspx#_Toc514058498
A very common mistake is to create an appdomain, and then execute something like Assembly a = myAppDomain.Load("someAsm.dll"); this has the effect of loading the assembly in both appdomains. This link has some examples of how to do what you want. http://www.gotdotnet.com/team/clr/AppdomainFAQ.aspx#_Toc514058498
