I was actually hoping for something like LogManager.IsShutdown;
Dru -----Original Message----- From: Graham Innocent [mailto:[EMAIL PROTECTED] Sent: Sunday, December 19, 2004 5:08 AM To: Log4NET User Subject: Re: Why does log4net.LogManager.Shutdown() throw an exception? Search your codebase for all instances of LogManager.Shutdown, put breakpoints on them, then run the code in the debugger. Cheers, Graham Innocent Parthenon Computing +44-1865-811184 http://www.parthcomp.com Dru Sellers wrote: > How would I check that? > Dru > > -----Original Message----- > From: Graham Innocent [mailto:[EMAIL PROTECTED] > Sent: Saturday, December 18, 2004 2:08 PM > To: Log4NET User > Subject: Re: Why does log4net.LogManager.Shutdown() throw an exception? > > Dru Sellers wrote: > >>- $exception {"Object reference not set to an instance of an object." >>} System.NullReferenceException >>When I try to close LogManager why does it throw an exception? >> >>--- >>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 >> > > > Is it possible that LogManager.Shutdown() has already been called ? > > > Cheers, > Graham Innocent Parthenon Computing > +44-1865-811184 http://www.parthcomp.com --- Incoming 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 --- 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
