logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter A. Kirk" ...@alpha-solutions.dk>
Subject RE: Different versions
Date Mon, 01 May 2006 19:17:07 GMT
Hi, thanks for the reply.

Actually I do not have control over the things which use log4net. 

My application is installed in the CMS which uses an older version of
log4net. My application also uses a "framework" which is built against a
newer version of log4net. These versions of log4net clash which appears
to mean that the cms and the framework cannot coexist - because of a 3rd


> -----Original Message-----
> From: Hart, Aaron [mailto:ahart@zolldata.com]
> Sent: 1. maj 2006 17:03
> To: Log4NET User
> Subject: RE: Different versions
> 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
> 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,
> try strong naming it and putting it in the GAC and leaving the cms's
> version in place.
> Aaron
> -----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
> Hi
> 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
> but
> version This causes problems with my classes - I get an error
> like:
> Could not load file or assembly log4net, version=, culture=...
> The
> 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
> the
> cms complains (same sort of error as above but with different dll
> version).
> How can I get the cms and my classes to use their own versions of
> log4net.dll?
> Thanks,
> Peter

View raw message