logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hart, Aaron" <ah...@zolldata.com>
Subject RE: Different versions
Date Mon, 01 May 2006 15:02:33 GMT
Since the two applications are built against two different versions of
log4net, the only way to run them both is to put both (or at least one?)
in the Global Assembly Cache, which requires you to strong name one of
them. It sounds like all you have control over is the newer version, so
try strong naming it and putting it in the GAC and leaving the cms's
version in place.


-----Original Message-----
From: Peter A. Kirk [mailto:pk@alpha-solutions.dk] 
Sent: Monday, May 01, 2006 4:53 AM
To: Log4NET User
Subject: Different versions


This isn't really an issue about log4net, but two programs which use
log4net, but I hope someone can offer some advice.

I have some classes which use log4net (ver These classes run 
inside a cms-framework - which apparently also uses log4net internally,
version This causes problems with my classes - I get an error
Could not load file or assembly log4net, version=, culture=...
located assembly's manifest definition does not match the assemply 
reference. (exception from HRESULT: 0x80131040).

If I replace the cms's version of log4net.dll with the one I use, then
cms complains (same sort of error as above but with different dll

How can I get the cms and my classes to use their own versions of 


View raw message