Here is a link to the DotNet.Commons project. One of the sub-projects is DotNet.Commons.Logging. They've implemented a unified ILog with implementations for log4net, EntLib Logging, and another basic text file logger:
http://www.gotdotnet.com/Workspaces/Workspace.aspx?id=e5546f13-1ced-47d1-8667-53b613cc4873 --- Nicko Cadell <[EMAIL PROTECTED]> wrote: > Ron, > > It sounds like you have done the right thing for your requirements. > You can essentially just copy the ILog interface, the LogImpl class > and the LogManager class into your own project and use your version > instead. > > You may want to dispense with the ILog interface altogether and just > return strongly typed LogImpl (or you could rename this to Log) > objects. If your Log object is sealed and its methods are not virtual > then your should get a small per-call performance boost by doing > this. The improvement will be small so it may not be worth changing > your existing code. > > As far as providing a logging fa�ade that allows different logging > implementations to be selected at runtime the log4j project has setup > a separate slf4j - Simple Logging Facade for Java (www.slf4j.org) > project to combine the efforts of the log4j team with the > commons-logging team. I think that this will provide a useful design > pattern if we need to go in that direction. > > Cheers, > > Nicko
