Ron,
I wanted to post this after I saw your commit, but I forgot.
I don't think we should confront users of log4net with our internal changes,
and hereby force them to have different config files for .NET 1.x and .NET
2.0.
Instead, I think we should convert from semi-colon to comma
I agree. I'll update the code.
For those of use that spelunked the code w/reflector (or looked at the source)
and now use commas, might I suggest you support both.
-Walden
--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Hello,
I'm very interested in using log4net as my companies standard logging utility.
Since our focus is primarily on developing web applications using asp.net, I'm
very interested in the AspNet*PatternConverter classes that Ron started to
implement back in October 2006. Is there a new
I'm still working on them. What functionality are you looking at using?
- Original Message
From: Jon Sheldon [EMAIL PROTECTED]
To: log4net-user@logging.apache.org log4net-user@logging.apache.org
Sent: Thursday, August 28, 2008 4:07:28 PM
Subject: Whatever happened to asp.net pattern
I think I've got an approach. I'm going to implement my own converter classes,
and then just include them in the config file as part of the layout declaration.
I'm pretty new to log4net, but does that sound like a reasonable approach?
Jon
From: Ron Grabowski [mailto:[EMAIL PROTECTED]
Sent:
I found an archived post (from 2006) in which Nicko states that log4Net
does not provide any method of persisting dynamic configuration changes.
Has anyone written any code to persist configuration changes that they
would be willing to share or at least talk about?
Thanks
