t: RE: Feedback for log4net.Contrib.AspNetPatternConverters
>
> I don't know why I didn't think of this sooner...if you have groups of
> related converters that you'd like to register the amount of
> additional
> xml nodes makes
I don't know why I didn't think of this sooner...if you have groups of
related converters that you'd like to register the amount of additional
xml nodes makes for some ugly xml:
A cleaner alternative is to group related converters into a layout:
public class AspNetPattern
Ron,
This does look like a very nice idea and does provide additional
functionality that log4net does not have out of the box.
I think that it makes sense to be able to register new converters into
the pattern layout on a per-repository basis. I will need to think about
where that would be store
Hello. In response to Nicko's reply to my first post on the log4net
list:
http://tinyurl.com/a24cc
http://www.mail-archive.com/log4net-user%40logging.apache.org/msg00886.html
I've written a collection of PatternConverter classes to make log4net
play nicely with Asp.Net. They allow for properties
