In general, if you are trying to use a specific version of an assembly the below doesn't really apply, you should just use the version you need.
However, sometimes you can run into a situation where you have this:
AssemblyX - references version 1.2.1 of AssemblyZ
AssemblyY - references version 1.2.2 of AssemblyZ
But your project needs both AssemblyX and AssemblyY.
So how do you resolve this? You can either put 1.2.1 and 1.2.2 of AssemblyZ in the GAC, or, if you're sure there aren't any compatibility issues, you can use assembly rebinding. Here's an example (this goes in your Web.config
or App.config
file):
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="myAssembly"
publicKeyToken="32ab4ba45e0a69a1"
culture="neutral" />
<bindingRedirect oldVersion="1.0.0.0"
newVersion="2.0.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
What this basically says is that if any assemblies in your solution reference 1.0.0.0 of myAssembly, then they should really use version 2.0.0.0. And you're expected to have version 2.0.0.0 present in the path.
A hack you can use when you always want them to use a specific version of the assembly is to specify a version range, like this:
<dependentAssembly>
<assemblyIdentity name="MyAssembly" publicKeyToken="B7567367622062C6" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-3.0.0.0" newVersion="1.2.1.0" />
</dependentAssembly>
This will force version 1.2.1.0 of MyAssembly to be used for any version reference of MyAssembly between 0.0.0.0 and 3.0.0.0.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…