How to resolve "The located assembly's manifest definition does not match the assembly reference." error?

Question

I downloaded source code for pdfiumviewer from git hub. I made changes to one of the projects in that solution.Then I added that project to my application and added reference of that project to one my application's project.I had to uncheck the Signing option for the PDfiumViewer project, as some of the dll in that project are unsigned.I am able to build the application successfully.But at run time when I create an object of one of the class of PDfiumviewer project.It gives me the following error:

Could not load file or assembly 'PdfiumViewer, Version=2.11.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

The version number of the assembly is correct.So, why am I getting this error?

Answer 1

问题是我已经将旧的未修改 PdfiumViewer dll 的引用添加到另一个项目中。因此，在运行时两个 dll（旧的和自定义的）之间存在冲突。我删除了旧的 dll 引用并且它起作用了。

Answer 2

Ive also encountered this issue, my scenario was thou that I had to add a reference from another solution into my project removing the reference was not an option - what worked for me was reinstall SQLclient from nuget package managerer on both solution. Hopes it helo someone else

Answer 3

我写了一个程序来自动修复这个问题： https : //github.com/BackTrak/DependencyFixup/releases/tag/1.0.0.0

Answer 4

The issue here is that you have a library that references v2.11.0.0 of the Pdfium library. This library could be an assembly that you built earlier, or another assembly that came from Pdfium that references this version of the library. When you built your version of the library you probably didn't use this same version number, and it wouldn't have been strong named correctly. To fix this, you can add an assembly binding redirect in your applications configuration file to redirect the offending library to your custom built one.

I wrote a program to fix this issue automatically: https://github.com/BackTrak/DependencyFixup/releases/tag/1.0.0.0

I know this question is old, but hopefully this helps out others!