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


  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?


Ответы (2)

Why are binding redirects needed at all? Suppose you have application A that references library B, and also library C of version Library B in turn also references library C, but of version 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 for an example of full config file):



You can also specify a range of versions to map:


Now library B, which was compiled with reference to C of version will use C of version 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.

We came across an issue with binding redirect for NewtonSoft.Json. We looked up the file version in win 10 file properties "", 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.


The result of above is.

Major  Minor  Build  Revision

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

9      0      0      0

See References:

How can i see the assembly version of a .NET assembly in Windows Vista and newer (WIndows 7, 2008)?

enter image description here

2022 WebDevInsider