The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Question

After signing the third parties assemblies and adding them to GAC I am getting the below error: also the Assembly Binder Log Entry shows this error

It says mismatching assemblies not sure how mistnaching as I deleted all obj and bin fold and batch built the application + reimported the dlls.

 Assembly manager loaded from:  C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Running under executable  C:\Program Files (x86)\Common Files\Microsoft Shared\DevServer\11.0\WebDev.WebServer40.exe

--- A detailed error log follows. 
=== Pre-bind state information ===
LOG: User = AKBARCA\user

LOG: DisplayName = ClubStarterKit.Core, Version=3.0.1.0, Culture=neutral, PublicKeyToken=null
 (Fully-specified)

LOG: Appbase = 

file:///C:/Users/user/Desktop/NhibernateMediumTrust/NhibernateMediumUpgrade/direct/clubstar

terkit v3 preview/ClubStarterKit.Web/

LOG: DEVPATH = C:\ProgramData\Red Gate\.NET Reflector\DevPath

LOG: Initial PrivatePath = 

C:\Users\user\Desktop\NhibernateMediumTrust\NhibernateMediumUpgrade\direct\clubstarterkit v3 preview\ClubStarterKit.Web\bin
Calling assembly : ClubStarterKit.Web, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null.

Solution 1

From my experience, this happens, usually once you've published your app and when you have different versions of nuget packages in play. If this happens to be your situation as well, the best way I've found to fix it is to right-click the solution (not the individual projects) and choose "Manage Nuget Packages". Then, locate the offending assembly in the installed packages. You'll probably see it listed multiple times. Click "Manage" on each of the older versions of the package and uncheck all your projects. Once only the latest version of the package remains in the list. Click "Manage" on this one and recheck any projects that need the package. This will essentially upgrade them all to use the same version of the package and should resolve your mismatch error.

Solution 2

I faced similar problem. In my case, I was having multiple projects in my solution.

One of the project was referring EntityFramework 4.0 and that project was being referred in another project that was referring to EntityFramework 5.0. I brought them in sync and the problem got away.

Solution 3

Hum... I faced something similar with the same error message.

In my case I've updated manually the version of the assemblies.

In the referenced assembly I had another version...

So, I updated it in the web.config.

This solved my problem.

Your === Pre-bind state information === seems incomplete. Generally it shows the execution and the last line shows the error, so, we can help only sharing our experiences. Example:

I hope someone else facing this problem find this helpful.

Solution 4

In my case, the error happens when the version specified in web.config's <bindingRedirect> of the dependent assembly (e.g. Newtonsoft.Json) doesn't match the version that is actually in the bin folder. Once the version number in the web.config is updated, the problem is fixed.

Solution 5

When I experienced this problem in the past, I deleted all my project's dll's from the gac, rebuilt the solution, then did iisreset and it was solved.

View more solutions

Comments

[lioni jordan]

"locate the offending assembly in the installed packages" no assemblies or package is listed or installed in Manage Nuget Packages. It is only giving option to install Jquery, Entityframwork.etc..

[Chris Pratt]

You've clicked the "Installed" link on the left, correct? Do you have page numbers at the bottom of the list?

[Chris Pratt]

Those errors are completely different than the one you posted in the your question. Those literally mean your project is missing that assembly. Just add the reference and you're good.

[lioni jordan]

When I run in VS i get this message: abudhabieuropcar.com/error.jpg in the browser the message is different: abudhabieuropcar.com/3.jpg I googled the issue, delay signing is one of the option, could delay signing solve the problem