ly determine if
> DOMConfigurator.Configure() failed
>
> Hi
>
> I've read the FAQ which tells this :
> "However, log4net will output a single message to
> System.Console.Error indicating that logging can not be performed."
>
> Is there a way to prog
Hi
I've read the FAQ which tells this :
"However, log4net will output a single message to System.Console.Error
indicating that logging can not be performed."
Is there a way to programmatically (rather than visually) diagnose a
log4net initialisation failure (especially through DOMConfigurator) ?
> "Log4NET User"
>
>
> To Log4NET User
>
> cc
>
> Subject Re: DOMConfigurator.Configure()
>
>
>
>
>
>
>
> Thanks Nicko
>
> I have the DomConfiguratorAtribute in my Assemblyinfo, yet it still
> doesn'
To
Log4NET User
cc
Subject
Re: DOMConfigurator.Configure()
Thanks Nicko
I have the DomConfiguratorAtribute in my Assemblyinfo, yet it still
doesn't work as expected. At least when run through NUnit.
Based on the Caveat you just mentioned I wonder if perhaps Nunit is interfering.
; -Original Message-
> > From: Tom Willis [mailto:[EMAIL PROTECTED]
> > Sent: 17 November 2004 19:14
> > To: Log4NET User
> > Subject: DOMConfigurator.Configure()
> >
> > I bet this question gets asked a lot. But I'm not finding
&
ation Attributes' section in the
log4net-1.2.0-beta8/doc/manual/introduction.html file.
Cheers,
Nicko
> -Original Message-
> From: Tom Willis [mailto:[EMAIL PROTECTED]
> Sent: 17 November 2004 19:14
> To: Log4NET User
> Subject: DOMConfigurator.Configure()
>
> I bet
I bet this question gets asked a lot. But I'm not finding anything in
the archives. It's probably cuz I suck.
Anyway,
If there any way to set log4net up so that you do NOT have to call
DOMConfigurator.Configure() before the logging goodness stats
happening?
Or is this a pipe dream?
