'.NET Core - MSB3277: Found conflicts between different versions

I am having difficulty getting rid of the build warning:

warning MSB3277: Found conflicts between different versions of the same dependent assembly that could not be resolved

specifically in .NET core projects.

In a full .NET framework project I would add some binding redirects so I googled around that issue and found this answer suggesting adding the following to the .csproj file:

<PropertyGroup>
  <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
  <GenerateBindingRedirectsOutputType>true</GenerateBindingRedirectsOutputType>
</PropertyGroup>

I have done this but to no avail - I still get the build warnings. Anything else I can do?

c++sharpmsbuild.net-coredotnet-cli


Solution 1:[1]

Run Update-Package via Package Manager Console, this will fix MSB3277, what it does it reinstall all the packages with highest version possible.

More info on official docs https://docs.microsoft.com/en-us/nuget/consume-packages/reinstalling-and-updating-packages

Solution 2:[2]

I had the same issue. Got several warnings on one of the projects. I updated all packages from the solution level and warnings went away. I used the Visual Studios for Mac to update the package. Right click the solution, then Update Nuget Packages.

Solution 3:[3]

Does any of you dependencies use <PrivateAssets>?

If project A has a private reference, and both the private reference and another reference requires some package X, but the private one requires a higher version of package X, then the assembly for project A will also require the higher version of package X. However you end up with a situation where any other project, e.g. project B, that references project A will only see the lower version of package X as a dependency - hence select the lower version of the assembly of package X to be copied to the output directory. The good news is that this DLL-HELL is detected at build time, where it sees that assembly projectA.dll requires a different projectX.dll than the one already designated as primary, and thus it logs some very unhelpful output about packageX being required by itself, which makes no sense... and gives up the build.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 Aistis Taraskevicius
Solution 2 Gunnsticles
Solution 3

Related Questions