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.
"Ollie Riches" <ol**********@phoneanalyser.net> wrote in message news:uj**************@TK2MSFTNGP12.phx.gbl...
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/de...ngredirect.asp
HTH
Ollie Riches
"Bob" <ms****@hotmail.com> wrote in message
news:e0**************@TK2MSFTNGP12.phx.gbl... 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.
"Neo" <ts******@gmail.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com... 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?