Binding redirect for System.Net.Http doesn't work - why?

▲
7
▼

The project I'm working on has System.Net.Http version 4.3.3 installed, according to NuGet. It had a binding redirect in the Web.config file to redirect it to version 4.2.0.0, which worked for some reason:

<dependentAssembly>
    <assemblyIdentity name="System.Net.Http" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-4.2.0.0" newVersion="4.2.0.0" />
</dependentAssembly>

I changed it to point to 4.3.3.0 which is the version NuGet says is installed:

<dependentAssembly>
    <assemblyIdentity name="System.Net.Http" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-4.3.3.0" newVersion="4.3.3.0" />
</dependentAssembly>

... but now I get this error when I try to debug the ASP.NET site:

Could not load file or assembly 'System.Net.Http' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

=== Pre-bind state information ===
LOG: DisplayName = System.Net.Http
 (Partial)
WRN: Partial binding information was supplied for an assembly:
WRN: Assembly Name: System.Net.Http | Domain ID: 2
WRN: A partial bind occurs when only part of the assembly display name is provided.
WRN: This might result in the binder loading an incorrect assembly.
WRN: It is recommended to provide a fully specified textual identity for the assembly,
WRN: that consists of the simple name, version, culture, and public key token.
WRN: See whitepaper http://go.microsoft.com/fwlink/?LinkId=109270 for more information and common solutions to this issue.
LOG: Appbase = file:///C:/.../Dev/Src/Web/PortalSite/
LOG: Initial PrivatePath = C:\...\Dev\Src\Web\PortalSite\bin
Calling assembly : (Unknown).
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\...\Dev\Src\Web\PortalSite\web.config
LOG: Using host configuration file: C:\...\Documents\IISExpress\config\aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.
LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
LOG: Attempting download of new URL file:///C:/.../AppData/Local/Temp/Temporary ASP.NET Files/vs/e31848dc/3694ba06/System.Net.Http.DLL.
LOG: Attempting download of new URL file:///C:/.../AppData/Local/Temp/Temporary ASP.NET Files/vs/e31848dc/3694ba06/System.Net.Http/System.Net.Http.DLL.
LOG: Attempting download of new URL file:///C:/.../Dev/Src/Web/PortalSite/bin/System.Net.Http.DLL.
LOG: Using application configuration file: C:\...\Dev\Src\Web\PortalSite\web.config
LOG: Using host configuration file: C:\...\Documents\IISExpress\config\aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config.
LOG: Redirect found in application configuration file: 4.2.0.0 redirected to 4.3.3.0.
LOG: Post-policy reference: System.Net.Http, Version=4.3.3.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
LOG: Attempting download of new URL file:///C:/.../AppData/Local/Temp/Temporary ASP.NET Files/vs/e31848dc/3694ba06/System.Net.Http.DLL.
LOG: Attempting download of new URL file:///C:/.../AppData/Local/Temp/Temporary ASP.NET Files/vs/e31848dc/3694ba06/System.Net.Http/System.Net.Http.DLL.
LOG: Attempting download of new URL file:///C:/.../Dev/Src/Web/PortalSite/bin/System.Net.Http.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Minor Version
ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.

To make things even more confusing, the DLL version in the bin directory for the site seems to be different again:

PS C:\...\Dev\Src\Web\PortalSite\bin> (Get-Item ...\bin\Debug\System.Net.Http.dll).VersionInfo

ProductVersion   FileVersion      FileName
--------------   -----------      --------
4.6.25908.02 ... 4.6.25908.02     C:\...\Dev\Src\Web\PortalSite\bin\System.Net.Http.dll

What's up with this? How did the redirect work before, and why doesn't it work now?

c#
asp.net
nuget
asked on Stack Overflow Mar 5, 2018 by Jez

5 Answers

▲
6
▼

It turns out that the DLL version in my bin directory was actually version 4.2.0.0, which is apparently bundled with Visual Studio 2017, and the version distributed in NuGet package version 4.3.3 is DLL version 4.1.1.2, which wasn't being used at all. Confusing! But this explains why the redirect to DLL version 4.2.0.0 worked and redirecting to 4.3.0.0 didn't.

answered on Stack Overflow Mar 5, 2018 by Jez
▲
3
▼

do not use any bindingRedirect for System.Net.Http , remove from config file and do not think witch version is in use, this is managed by your system

i found that adding it to config file cause serious problem, because each file use diffrent version of this dll.

REMOVING System.Net.Http FROM CONFIG resolve my insane problem that cause errors and not found assembly .

answered on Stack Overflow Jul 22, 2020 by Mahdi
▲
0
▼

I had similar issue in past. Most probably you have other assemblies in your .csproj which still have dependency on old version i.e. 4.2.0.0

answered on Stack Overflow Mar 5, 2018 by rahulaga_dev
▲
0
▼

Ya exactly. The nuget versions and the dll's assembly versions are different. Make sure you understand the difference clearly.

A nuget package maybe 4.1.1 and the assembly version of the dlls inside it needn't be 4.1.1 or anything related to 4.1.1.

We specify dll versions in all the dll references. And nuget references are made so that once the project is building, the required dlls are made available in the packages, so that it can be taken and moved to the local bin for the compiler to use.

answered on Stack Overflow Apr 15, 2018 by Adarsh P. S.
▲
0
▼

You can also change the newVersion to the version that exists currently in your project:

  1. search for System.Net.Http string in Search solution Explorer inside VS and find the version of this assembly by checking property of that dll or reference by checking property window(f4)

  2. change the newVersion to the one that exists in your project. for example 4.4

     <bindingRedirect oldVersion="0.0.0.0-4.3.3.0"  newVersion="4.4"  />

sometimes removing the whole depencency like the answer by @Mahdi helps https://stackoverflow.com/a/63031440/184572

answered on Stack Overflow May 18, 2021 by Iman

User contributions licensed under CC BY-SA 3.0