Mailing-List: contact log4net-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4NET User" <log4net-user@logging.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Different versions
Date: Mon, 1 May 2006 21:17:07 +0200
Message-ID: 
 <5C243BD898DAAF45813B837ADC5B866B37E1A0@alpha-srv200.as1.alphasolutions.dk>
Thread-Topic: Different versions
Thread-Index: AcZqwZXk/X8DahUFQQqXJNG1UPnCxgCS4v6gAAinfkAACOhrIA==
From: "Peter A. Kirk" <pk@alpha-solutions.dk>
To: "Log4NET User" <log4net-user@logging.apache.org>

Hi, thanks for the reply.

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

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
dll!=20


Peter


> -----Original Message-----
> From: Hart, Aaron [mailto:ahart@zolldata.com]
> Sent: 1. maj 2006 17:03
> To: Log4NET User
> Subject: RE: Different versions
>=20
> 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.
>=20
> Aaron
>=20
> -----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
>=20
> Hi
>=20
> This isn't really an issue about log4net, but two programs which use
> log4net, but I hope someone can offer some advice.
>=20
> I have some classes which use log4net (ver 1.2.9.0). These classes run
> inside a cms-framework - which apparently also uses log4net
internally,
> but
> version 1.2.0.3. This causes problems with my classes - I get an error
> like:
> Could not load file or assembly log4net, version=3D1.2.9.0, =
culture=3D...
> The
> located assembly's manifest definition does not match the assemply
> reference. (exception from HRESULT: 0x80131040).
>=20
> 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).
>=20
> How can I get the cms and my classes to use their own versions of
> log4net.dll?
>=20
>=20
> Thanks,
> Peter