This is a bug in log4net config file parsing. Currently you need to use
double backslashes to resolve this.
Nicko
> -Original Message-
> From: Joe Joe [mailto:[EMAIL PROTECTED]
> Sent: 09 November 2004 17:34
> To: log4net-user@logging.apache.org
> Subject: Use of backslash in file paths
How about simply using forward slashes? Our file appender section looks
like this
logs/publicweb.log" />
and works properly. If you're concerned that your ops people need a
reminder, you can always add a comment.
Jo
I know I can work around it by doubling the backslashes or using forward
slashes.
But I'm concerned my administrators won't always remember to do this - as
they don't generally need to double backslashes in filenames in .NET config
files.
Why does it behave like this? Is it a bug?
You need to
You need to double up the backslashes:
On Tue, 09 Nov 2004 17:34:23 +, Joe Joe <[EMAIL PROTECTED]> wrote:
> Log4Net 1.2.0 Beta 8 doesn't seem to like backslashes in filenames - e.g.
> the following example results in output to "logTrace.log" instead of
> "log\Trace.log":
>
> type=
