There are several ways in which you can control which messages go to
which appender.
If you want to route messages from 2 different loggers to 2 different
files then you can do:
...
..
If you want to control the logging on the message level you can set a
th
Leo,
I've attempted to reproduce this error, but I'm not having any
luck. Could you switch on log4net internal debuging (see
http://logging.apache.org/log4net/release/manual/faq.html#internalDebug
for details). This will produce a large amount of diagnostic output, but
the message you are i
The best bet would be to enable internal debug:
http://logging.apache.org/log4net/release/manual/faq.html#internalDebug
As you are running under ASP.NET you will need to use the sysinternals
dbgview app to see the output.
Nicko
> -Original Message-
> From: Cheng [mailto:[EMAIL PROTECTE
The error is being thrown because Directory.InternalCreateDirectory
cannot see the directory root. Why this is I don't know. It isn't a code
access security issue. It may be an NTFS permissions issue.
What happens if you create a console app that calls:
System.IO.Directory.CreateDirectory("f:\\Lo
See
http://logging.apache.org/log4net/release/manual/faq.html#HC-14456678.
This is nothing to get upset about. Really, we're talking about doing
the same thing two different ways. Log4net's approach is minimal,
Nlog's is maximal. The minimal approach requires more code to call, but
allows for a
