Assembly Binding redirect: How and Why?

This is not a problem question but a general understanding question on assembly binding redirect's working.

**Queries**

1. Why binding redirect shows only major version and not minor, build and revision numbers?
2. Does old and new version change only when there is change in major version?

<dependentAssembly>
<assemblyIdentity name="FooBar"
publicKeyToken="32ab4ba45e0a69a1"
culture="en-us" />

<bindingRedirect oldVersion="7.0.0.0" newVersion="8.0.0.0" />
</dependentAssembly>

We came across an issue with binding redirect for NewtonSoft.Json. We looked up the file version in win 10 file properties "9.0.1.19813", looked up the number and the redirect kept failing. Further investigation and found that we were looking at file version and not assembly version. So, I wonder if people are mistaking File Version (which changes often) and Assembly version (which you can't see in windows 10 File Explorer). To see the Assembly version of a dll you can run this in powershell. **Replace the dll name with the one you want to find version for.**

[Reflection.AssemblyName]::GetAssemblyName('C:\development\bin\Newtonsoft.Json.dll').Version

The result of above is.

Major Minor Build Revision

----- ----- ----- --------

9 0 0 0



**See References:**

[To see links please register here]

[To see links please register here]

[![enter image description here][1]][1]


[1]:

Why are binding redirects needed at all? Suppose you have application A that references library B, and also library C of version 1.1.2.5. Library B in turn also references library C, but of version 1.1.1.0. Now we have a conflict, because you cannot load different versions of the same assembly at runtime. To resolve this conflict you might use binding redirect, usually to the new version (but can be to the old too). You do that by adding the following to app.config file of application A, under `configuration > runtime > assemblyBinding` section (see [here][1] for an example of full config file):

<dependentAssembly>
<assemblyIdentity name="C"
publicKeyToken="32ab4ba45e0a69a1"
culture="en-us" />

<bindingRedirect oldVersion="1.1.1.0" newVersion="1.1.2.5" />
</dependentAssembly>

You can also specify a range of versions to map:

<bindingRedirect oldVersion="0.0.0.0-1.1.1.0" newVersion="1.1.2.5" />

Now library B, which was compiled with reference to C of version 1.1.1.0 will use C of version 1.1.2.5 at runtime. Of course, you better ensure that library C is backwards compatible or this might lead to unexpected results.

You can redirect any versions of libraries, not just major ones.


[1]:

[To see links please register here]

I highly recommend to use dotPeek from JetBrains to look at dll library and it's version.
According your second question. Versions can be absolutely different, not only major versions count.
[enter image description here][1]


[1]: