ansaurus

Question

What is the best approach to use 3rd party that uses another version of other 3rd party (log4net) already used in the system?

Answer 1

+2 A:

The recommended approach would be to install both versions of log4net into the Global Assembly Cache (GAC).

If however you can't change the requirement of loading all assemblies from a single folder, it is probably easiest to rename the copy of log4net used by your projects and reference the renamed version.

0xA3 2010-10-04 10:14:17

Yeah, it makes sense. Will see if others have some different ideas. Thanks.

Andriy Buday 2010-10-04 10:20:37

Having all in GAC helps, but indeed that is something we don't want to do.

Andriy Buday 2010-10-06 12:32:40

Renaming one copy of the assembly also doesn't help.

Andriy Buday 2010-10-06 12:33:06

Someone has suggested to use privatePath, but it also doesn't help. So .net allows me use private path and define two pathes to two assemblies but with different versions of log4net and it is loaded at runtime just fine, but when my code requires another version of log4net it doesn't load it, maybe because it thinks that it already has loaded.Ordering is taken into account, so if I have following:< probing privatePath="log4net129;log4net1210;" / >it will load version 1.2.9.0 and will NOT load 1.2.10.0, but will fail once I need it.All depends on which version I demand first :)Very funny!

Andriy Buday 2010-10-06 12:35:07

Since GAC suggestion is something I like and it works, but still not sure to what decision my team will come I accept this answer. Thanks!

Andriy Buday 2010-10-06 12:38:36

Answer 2

+2 A:

I don't know what the changes are between the two versions (we use 1.2.10.0 ourselves) but if the interfaces have not changed then you could try an assembly redirect to the newer version:

<configuration>
   <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
       <dependentAssembly>
         <assemblyIdentity name="log4net"
                           publicKeyToken="b32731d11ce58905"
                           culture="neutral" />
         <bindingRedirect oldVersion="1.2.9.0"
                          newVersion="1.2.10.0"/>
       </dependentAssembly>
      </assemblyBinding>
   </runtime>
</configuration>

Make sure that the key is the same as the one I provided as they may have changed between the two.

http://msdn.microsoft.com/en-us/library/7wd6ex19(VS.71).aspx

Bronumski 2010-10-04 10:22:04

Cool, I did not know about this! You rock!

Andriy Buday 2010-10-04 10:27:11

I'm actually not sure if you can do this now. If the keys are different between the two versions then it will not work.

Bronumski 2010-10-04 10:37:25

I have to check this. I will post comment once will have results.

Andriy Buday 2010-10-04 11:23:21

This approach doesn't work. Accordiongly to this http://stackoverflow.com/questions/2191296/net-assembly-binding-redirect-with-differing-public-key-tokens we cannot redirect between assemblies with different publicKeyToken. 1.2.10.0 has token "1b44e1d426115821" (sadly, but not equal to "b32731d11ce58905"). Also I'm still not sure if this will work outside of the GAC.

Andriy Buday 2010-10-06 07:24:08

ansaurus

tags:

views:

answers:

What is the best approach to use 3rd party that uses another version of other 3rd party (log4net) already used in the system?

related questions