An error used to be generated for this, but so many people complained
about this that it was reduced to a debug message.
If is set then the
following debug message is reported:
log4net: Logger: No appenders could be found for logger
[TestConsoleApp.LoggingExample] repository [log4net-default-
Is this what you are looking for?
http://logging.apache.org/log4net/release/manual/faq.html#internalDebug
Thanks,
Surya
On 6/9/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Ron,I agree that log4net should never raise an exception. But my suggestion isthat it should atleast log some message
Ron,
I agree that log4net should never raise an exception. But my suggestion is
that it should atleast log some message to signal that Configure has not
been called.
Thanks,
Hemant
Ron Grabowski writes:
log4net should never raise an exception. Its been designed to not
interfere with you
log4net should never raise an exception. Its been designed to not
interfere with your application. If you do not call Configure, log4net
will not configure itself.
--- [EMAIL PROTECTED] wrote:
>
> Hi
>
> I would like to know what will happen if I get a logger using
> LogManager and
> make a l
