Yes, you can provide your own ILog, LogImpl, etc. I've been doing this for a while and posted a question:
http://www.mail-archive.com/log4net-user%40logging.apache.org/msg01677.html asking if this was still the recommended way to do things in the latest version. The other link in that thread has examples of what those three classes could look like: http://tinyurl.com/cssnd http://cvs.apache.org/viewcvs.cgi/logging-log4net/extensions/net/1.0/log4net.Ext.Trace/cs/src There's nothing special about the 1.0 notation. Its just to show that log4net is flexible and that the code can be applied to both versions of the .Net Framework. --- Schweizer Andreas <[EMAIL PROTECTED]> wrote: > Hi list, hi Ron! > > first, thank you Ron for your detailed answer. > > > It sounds like designing and implementing your own interface > > (using ILog as a guide) might suit your needs better. Here is > > an example of an > > That's exactly true. If I understand it correctly, we can then > simply provide our own customized ILog, LogImpl and LogManager. > That's really nice :-)
