NHibernate solved that by building a logging proxy into NHibernate.dll
and then dynamically binding to log4net.
Are the licenses compatible? You could borrow their implementation.
Richard
On 18 May 2011, at 23:26, Ryan Boggs rmbo...@gmail.com wrote:
The problem isn't NAnt targeting
Hi,
See inline...
On Wed, May 18, 2011 at 3:31 PM, Dominik Guder o...@guder.org wrote:
Am 18.05.2011 22:27, schrieb Martin Aliger:
I do not see problem _targeting_ net-4.0-client Framework. No real need to
be hosted in that, imho.
Martin
Hi,
+1. IMHO we could require full .net 4.0
NLog would be a nice replacement. Even though 2.0 is still listed as
beta, it claims to support .net 2.0sp1 and up, including client
profiles. But again, it would have to wait until .net 1.* runtime
support is dropped from NAnt (nlog dropped support for .net 1.*
starting with the 2.0 release).
Something else to look at. A quick google search says that nhibernate
is LGPL. I'm not sure which version though.
I am not a laywer but I would think that GPL (NAnt's current license)
and LGPL would be compatible. I would appreciate additional insight
if there are those who are more familiar
The 450 LOC which implement this can be seen here:
http://nhibernate.svn.sourceforge.net/viewvc/nhibernate/trunk/nhibernate/src/NHibernate/Logging.cs?revision=5132view=markup
It binds dynamically by using compiled linq expression trees.
Richard
On 19 May 2011, at 19:34, Ryan Boggs
