Dependency error (System.Net.Http) when using Azure deployment options - works when publishing in Visual Studio

▲
2
▼

I have a very weird situation I hope someone can help with!

I have a normal ASP.NET MVC website. I've set up "Deployment Options" to push to a domain on every Develop commit. However, this has started giving the dependency error: 

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)

Now, I thought this was some caching since solution worked locally. So I have been publishing the app inside Visual Studio a couple of times (with option of deleting all remote files), and then the solution works.

However, after doing this, and I go back to a normal commit with Deployment Options, I go back to the same error:

enter image description here

c#
asp.net
asp.net-mvc
azure
asked on Stack Overflow Aug 1, 2018 by Lars Holdgaard

3 Answers

▲
1
▼

From your description it seems like it has deployed successfully in past.

Have you upgraded project recently? If yes, look at this thread Strange issue with System.Net.Http 4.2.0.0 not found

Also, check if you are referencing DLL from NuGet and not GAC.

answered on Stack Overflow Aug 4, 2018 by r2018
▲
0
▼

First thing that comes to mind is that you added a new DLL in your solution that depends on another version of System.Net.Http assembly. If you know that you added a new DLL, check for its assembly dependency.

Another solution might be to manually specify the version of the assembly in code. And select SpecificVersion. (but I'm guessing it's the first thing that causes the issue).

answered on Stack Overflow Aug 1, 2018 by Iustinian Andrioaie
▲
0
▼

I have came across similar issue once. There should be a mismatch of the versions between System.Net.Http package.

Try verifying the version of System.Net.Http for the entire solution and refer the same version in all the projects.

This happens if a package is referenced in a project and different version of the same package is referenced in another project. Here, this error occurs when there is a reference between these two projects.

answered on Stack Overflow Aug 1, 2018 by Arunprabhu

User contributions licensed under CC BY-SA 3.0