Once an assembly is loaded into an AppDomain it cannot be unloaded. There is no way of releasing or unloading a specific assembly, this is because the .net runtime may have types from the assembly in memory or awaiting garbage collection. The only way to unload an assembly is to unload the AppDomain that it is loaded into. An AppDomain is sort of like the .net equivalent of a process, but you can have several within an OS process.
Chris Brumme has a far far more detailed explanation of how this all works. http://blogs.msdn.com/cbrumme/ Nicko > -----Original Message----- > From: Dru Sellers [mailto:[EMAIL PROTECTED] > Sent: 21 December 2004 16:56 > To: 'Log4NET User' > Subject: log4net assembly locked > > I am having difficulty with my application maintaining a lock > on the log4net assembly. > > I have called > > log4net.LogManager.Shutdown(); in the dispose of my > Application context as the last line. Yet I still have a lock > on the .dll > > Any thoughts? > > Dru > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.817 / Virus Database: 555 - Release Date: 12/15/2004 > > >
