prouse.org]
Sent: Thursday, August 19, 2010 2:42 PM
To: 'Log4NET User'
Subject: RE: Using my own implementation of ILog
If that is the case, then I would suggest the following.
1. Download the log4net source as a guide,
2. Derive an ILoggerWrapper class from LogImpl
: Sheffield, Julie [mailto:julie_sheffi...@intuit.com]
Sent: Thursday, August 19, 2010 2:26 PM
To: Log4NET User
Subject: RE: Using my own implementation of ILog
The data changes per request. I’d rather not have the caller be responsible
for adding this info to the logs—we need to make sure it’s
: 'Log4NET User'
Subject: RE: Using my own implementation of ILog
Extension methods can’t override existing methods, so you would need to
create/use new methods on ILog that chain to the underlying methods. For
example DebugWithProperties(…) -> Debug()
Do these properties ch
ext before the log calls and have them logged out that way?
Rob
From: Sheffield, Julie [mailto:julie_sheffi...@intuit.com]
Sent: Thursday, August 19, 2010 12:47 PM
To: Log4NET User
Subject: RE: Using my own implementation of ILog
I have some custom properties I want to stick
I have some custom properties I want to stick in LoggingEvent.Properties. Can
I do that with extension methods?
From: Rob Prouse [mailto:r...@prouse.org]
Sent: Thursday, August 19, 2010 12:38 PM
To: 'Log4NET User'
Subject: RE: Using my own implementation of ILog
Before you
:20 PM
To: log4net-user@logging.apache.org
Subject: Using my own implementation of ILog
I see examples for extending the ILog interface that involve a custom
version of the LogManager. However, is it possible simply to provide my own
implementation of the standard ILog interface and configure
I see examples for extending the ILog interface that involve a custom
version of the LogManager. However, is it possible simply to provide my
own implementation of the standard ILog interface and configure the
LogManager to return it? If so, how? I can certainly follow the
examples and write my
