StackTrace
at Spring.Context.Support.AbstractApplicationContext.Close()
at Cystem.Management.Context.Dispose(Boolean disposing)
at System.Windows.Forms.ApplicationContext.Finalize()
Here is the method I used to close my ApplicationContext
protected override void Dispose(bool disposing) { //disposing ==
false
base.Dispose (disposing);
MSINC.Plugins.PluginManager.UnloadAll();
cxt.Close(); //Spring.Context.IConfigurableApplicationContext
try {
log4net.LogManager.Shutdown(); //Green Debug Arrow Here
} catch (Exception ex) {
throw ex;
}
}
-----Original Message-----
From: Nicko Cadell [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 19, 2004 1:21 PM
To: Log4NET User
Subject: RE: Why does log4net.LogManager.Shutdown() throw an exception?
Dru,
Do you have the stack trace for the exception?
Nicko
> -----Original Message-----
> From: Dru Sellers [mailto:[EMAIL PROTECTED]
> Sent: 18 December 2004 15:53
> To: 'Log4NET User'
> Subject: Why does log4net.LogManager.Shutdown() throw an exception?
>
> - $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
>
>
>
---
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
