manifest definition does not match the assembly reference

[Bob]

I want to use a 3rd party assembly that links to a "4th party assembly." My
problem is that I use a newer version of that 4th party assembly. When I
add the assemblies as references to my application it won't run. I get an
error, " The located assembly's manifest definition with name 'XXX' does not
match the assembly reference.".

Is there any way to get around this? All the assemblies are strong named so
is there a way to use the GAC to solve this? Also I know the dll is
backwards compatible. Its only the .Net runtime that's having the problem
with the version numbers.

Thanks for the help.


Bob

 

[Neo]

My first question would be why would you you update the 4th party
asssembly at all. How do you know what the code changes in the 4th
party assembly will effect 3rd party code?

 

[Bob]

Because the vender claims its backwards compatable and there is a fix in the
newer version that I need. Like I said I also am using the 4th party
assembly directly.

 

[Ollie Riches]

I can't determine from your post whether your 3rd & 4th party
dll's\assemblies are .Net managed code or not but if they are have you
looked at binding redirecting in the app.config file?

http://msdn.microsoft.com/library/d.../en-us/cpgenref/html/gngrfbindingredirect.asp

HTH

Ollie Riches

 

[Bob]

Here is what the application dependency list looks like.



Application

│

├─► Assembly1.Net.dll Version 1.0.0.8

│

└─► Assembly2.Net.dll Version 1.0.0.0

│

└─► Assembly1.Net.dll Version 1.0.0.4




I know I can create a global pollicy using Mscorcfg.msc but I am using xcopy and don't have access to this.