C# Binding Redirects – Finding and Detecting Assembly Version of Any DLL
C# Binding Redirects – Finding and Detecting Assembly Version of Any DLL
When dealing with binding redirects, you may not know the newVersion value to use for a recently updated library. The file version of the DLL is not necessarily the assembly version of the DLL, and when it comes to binding redirects, you must use the correct assembly version for a particular library.
For example, in the web.config for one of our MVC projects we have the following:
<runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Antlr3.Runtime" publicKeyToken="eb42632606e9261f"> <bindingRedirect oldVersion="0.0.0.0-3.5.0.2" newVersion="3.5.0.2"> </dependentAssembly> </assemblyBiding> </runtime>
If we update the Antlr3.Runtime package to the latest version in the nuget package manager, our binding redirects may not be automatically updated. As such, we will have to update it manually ourselves with the correct newVersion assembly version value for the updated DLL. To find the assembly version, run this PowerShell script (updating the path to the DLL as necessary):
[Reflection.AssemblyName]::GetAssemblyName('C:\development\bin\Antlr3.Runtime.dll').Version
This is the version number that is needed for the updated binding redirect in the "newVersion" attribute.
Rent dedicated game servers from Chicago, Kansas City, Dallas Texas, Wilkes-Barre Pennsylvania, Arizona, Denver Colorado, California, Florida, and Sofia Bulgaria starting as low as $7.45 a month. We Be HostiN (https://webehostin.com)
Tags: assembly, binding, dll, find, finds, get, gets, redirect, retrieve, version