我得到类似的编译器错误。一旦我将dll文件的依赖项目添加到解决方案中，问题就解决了。

I recently hit this problem. In my case, I have NuGet packages on different assemblies. What I had was different versions of the same NuGet packages associated with my own assemblies. My solution was to use the NuGet package manager upon the Solution, as opposed to the individual projects. This enables a "consolidation" option, where you can upgrade your NuGet packages across as many projects as you want - so they all reference the same version of the assembly. When I did the consolidations, the build failure disappeared.

我就有这个问题。这是因为我有许多项目指向相同的组装，但从不同的版本。我解决它选择相同版本的所有项目在我的解决方案。

我也遇到了一些问题，我所要做的就是删除导致错误的.dll(可以在参考中找到)，并重新添加它。

效果非常好。

为任何人添加我的解决方案，这可能会有所帮助。

I had a ClickOnce solution throwing this error. The app referenced a common "Libs" folder and contained a project reference to a Foo.dll. While none of the projects in the solution referenced the static copy of the Foo.dll in the "Libs" folder, some of the references in that folder did (ie: my solution had refs to Libs\Bar.dll which referenced Foo.dll.) Since the CO app pulled all the dependencies from Libs as well as their dependencies, both copies were going into the project. This was generating the error above.

我通过将我的Libs\Foo.dll静态版本移动到一个子文件夹Libs\Fix\Foo.dll来解决这个问题。此更改使ClickOnce应用程序只使用DLL的项目版本，并且错误消失了。

帮助我的是，我进入包管理器解决方案，查看导致问题的安装包。我看到有几个项目引用了相同的包，但是版本不同。我根据自己的需要把它们排列起来，这很有效。