我想在上面的评论中发布pauloya提供的解决方案。我相信这是找到冒犯性引用的最佳解决方案。

最简单的方法找到什么是“冒犯的引用”是 设置生成输出的详细信息(工具，选项，项目和解决方案， 构建和运行，MSBuild项目构建输出详细信息)和 构建之后，在输出窗口中搜索警告。查看原文 就在它上面。

例如，当你在输出面板中搜索“冲突”时，你可能会发现这样的东西:

3>  There was a conflict between "EntityFramework, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089".
3>      "EntityFramework, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" was chosen because it was primary and "EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" was not.

正如您所看到的，EF版本5和6之间存在冲突。

我想在上面的评论中发布pauloya提供的解决方案。我相信这是找到冒犯性引用的最佳解决方案。

最简单的方法找到什么是“冒犯的引用”是 设置生成输出的详细信息(工具，选项，项目和解决方案， 构建和运行，MSBuild项目构建输出详细信息)和 构建之后，在输出窗口中搜索警告。查看原文 就在它上面。

例如，当你在输出面板中搜索“冲突”时，你可能会发现这样的东西:

3>  There was a conflict between "EntityFramework, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089".
3>      "EntityFramework, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" was chosen because it was primary and "EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" was not.

正如您所看到的，EF版本5和6之间存在冲突。

I just spent sometime debugging the same issue. Note, that issue might not be between different projects, but actually between several references in one project that depend on different versions of the same dll/assembly. In my case, issue was reference FastMember.dll versions mismatch that comes from two different NuGet packages in a single project. When I was given a project, it would not compile because NuGet packages were missing and VS refused to restore missing packages. Through the NuGet menu, I manually update all the NuGets to the latest version, that is when the warning appeared.

在Visual Studio工具中>选项>构建和运行> msbuild项目构建输出详细信息:(设置为)诊断。在“输出”窗口中查找有冲突的行。下面是我得到的输出部分:

1>  There was a conflict between "FastMember, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null" and "FastMember, Version=1.3.0.0, Culture=neutral, PublicKeyToken=null". (TaskId:19)
1>      "FastMember, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null" was chosen because it was primary and "FastMember, Version=1.3.0.0, Culture=neutral, PublicKeyToken=null" was not. (TaskId:19)
1>      References which depend on "FastMember, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null" [C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\FastMember.1.5.0\lib\net461\FastMember.dll]. (TaskId:19)
1>          C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\FastMember.1.5.0\lib\net461\FastMember.dll (TaskId:19)
1>            Project file item includes which caused reference "C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\FastMember.1.5.0\lib\net461\FastMember.dll". (TaskId:19)
1>              FastMember, Version=1.5.0.0, Culture=neutral, processorArchitecture=MSIL (TaskId:19)
1>      References which depend on "FastMember, Version=1.3.0.0, Culture=neutral, PublicKeyToken=null" []. (TaskId:19)
1>          C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\ClosedXML.0.94.2\lib\net46\ClosedXML.dll (TaskId:19)
1>            Project file item includes which caused reference "C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\ClosedXML.0.94.2\lib\net46\ClosedXML.dll". (TaskId:19)
1>              ClosedXML, Version=0.94.2.0, Culture=neutral, processorArchitecture=MSIL (TaskId:19)

注意，该项目文件项包括导致引用“C:\Users\ksd3jvp\Source\Temp\AITool\Misra\AMSAITool\packages\ClosedXML.0.94.2\lib\net46\ClosedXML.dll”

ClosedXML.dll来自ClosedXML NuGet，它依赖于FastMember.dll 1.3.0.0。在它之上，项目中还有FastMember Nuget，它有FastMember.dll 1.5.0.0。不匹配!

我已经卸载了ClosedXML和FastMember NuGets，因为我有绑定重定向，并安装了ClosedXML的最新版本，解决了这个问题!

基本上，当您引用的程序集将“Copy Local”设置为“True”时，就会发生这种情况，这意味着DLL的副本与exe一起放置在bin文件夹中。

由于Visual Studio也会复制所引用程序集的所有依赖项，因此最终可能会引用同一个程序集的两个不同构建。如果您的项目在不同的解决方案中，因此可以单独编译，则更有可能发生这种情况。

我解决这个问题的方法是在组装项目中将Copy Local设置为False。只针对可执行文件/web应用程序，在这些应用程序中，您需要运行成品的程序集。

希望这有意义!

也有这个问题-在我的情况下，这是由于有“特定版本”属性上的许多引用设置为真。在这些引用上将其更改为false就解决了这个问题。

如果你使用Nuget来管理依赖项，我还有另一种方法。我发现有时候VS和Nuget不匹配，Nuget无法识别你的项目不同步。的包。config会说一件事，但在References - Properties中显示的路径将指示其他内容。

如果你愿意更新你的依赖项，请执行以下操作:

From Solution Explorer, right click the Project and click 'Manage Nuget Packages' Select 'Installed packages' tab in left pane Record your installed packages You may want to copy your packages.config to your desktop first if you have a lot, so you can cross check it with Google to see what Nuget pkgs are installed Uninstall your packages. Its OK, we're going to add them right back. Immediately install the packages you need. What Nuget will do is not only get you the latest version, but will alter your references, and also add the binding redirects for you. Do this for all of your projects. At the solution level, do a Clean and Rebuild.

您可能希望从较低的项目开始，然后逐步到较高级别的项目，并在进行过程中重新构建每个项目。

如果你不想更新你的依赖项，那么你可以使用包管理器控制台，并使用语法update - package -ProjectName [yourProjectName] [packageName] -Version [versionNumber]