Solution 1) add common logging 2) at NH startup look for log4net.dll (start-up mean just before instantiate the bytecode-provider) 2a) where present autoconfigure common-logging/NH to work with log4net 3) for other logging framework we can just relay to common-logging configuration/restrictions.
On Mon, Aug 2, 2010 at 5:13 AM, Patrick Earl <[email protected]> wrote: > In my journey working to get NHibernate to work with the .NET client > profile, the only significant issue that remains (assuming NH-2263 is > accepted) is the logging framework. log4net has a dependency on > System.Web. There was previously discussion about logging > abstractions and using Common.Logging, but it seems that the > Common.Logging patch never got traction. Based on my reading of the > mailing list discussion it sounds like the preferred solution would > have no dependency on a third party framework and would feature an > NHibernate-specific pluggable logging system. Am I getting the right > idea? > > Are there any other qualms people have had with the current logging > techniques, or would a pluggable mechanism for supporting an ILog-like > interface be good? > > Patrick Earl -- Fabio Maulo
