Warning: Found conflicts between different versions of the same dependent assembly

.net warnings
ollifant picture ollifant · Aug 20, 2008 · Viewed 186.8k times · Source

I am currently developing a .NET application, which consists of 20 projects. Some of those projects are compiled using .NET 3.5, some others are still .NET 2.0 projects (so far no problem).

The problem is that if I include an external component I always get the following warning:

"Found conflicts between different versions of the same dependent assembly".

What exactly does this warning mean and is there maybe a possibility to exclude this warning (like using #pragma disable in the source- code files)?

Answer

Brian Low picture Brian Low · Jan 26, 2010

This warning means that two projects reference the same assembly (e.g. System.Windows.Forms) but the two projects require different versions. You have a few options:

  1. Recompile all projects to use the same versions (e.g. move all to .Net 3.5). This is the preferred option because all code is running with the versions of dependencies they were compiled with.

  2. Add a binding redirect. This will suppress the warning. However, your .Net 2.0 projects will (at runtime) be bound to the .Net 3.5 versions of dependent assemblies such as System.Windows.Forms. You can quickly add a binding redirect by double-clicking on error in Visual Studio.

  3. Use CopyLocal=true. I'm not sure if this will suppress the warning. It will, like option 2 above, mean that all projects will use the .Net 3.5 version of System.Windows.Forms.

Here are a couple of ways to identify the offending reference(s):

  • You can use a utility such as the one found at https://gist.github.com/1553265
  • Another simple method is to set Build output verbosity (Tools, Options, Projects and Solutions, Build and Run, MSBuild project build output verbosity, Detailed) and after building, search the output window for the warning, and look at the text just above it. (Hat tip to pauloya who suggested this in the comments on this answer).

Related questions

Unable to apply publish properties?

I don't know what caused Visual Studio to start thinking it needs to publish my project, but now whenever I build it, I get several "Unable to apply publish properties for item 'blah'" warnings. How do I stop Visual Studio 2005…

Read More
Accessing a member on Form may cause a runtime exception because it is a field of a marshal-by-reference class

Accessing a member on Form may cause a runtime exception because it is a field of a marshal-by-reference class I know what this warning is and know how to solve it. My question is why could this cause a runtime …

Read More
"Access of shared member, constant member, enum member or nested type through an instance"

I wonder why Visual Studio is raising this warning: Access of shared member, constant member, enum member or nested type through an instance My code: Dim a As ApplicationDeployment = deployment.Application.ApplicationDeployment.CurrentDeployment If System.Deployment.Application.ApplicationDeployment.IsNetworkDeployed Then …

Read More