Resolving MSB3247 – Found conflicts between different versions of the same dependent assembly

by

Change the “MSBuild project build output verbosity” to “Detailed” or above. To do this, follow these steps:

  1. Bring up the Options dialog (Tools -> Options…).
  2. In the left-hand tree, select the Projects and Solutions node, and then select Build and Run.
    • Note: if this node doesn’t show up, make sure that the checkbox at the bottom of the dialog Show all settings is checked.

  3. In the tools/options page that appears, set the MSBuild project build output verbosity level to the appropriate setting depending on your version:

  4. Build the project and look in the output window.

Check out the MSBuild messages. The ResolveAssemblyReferences task, which is the task from which MSB3247 originates, should help you debug this particular issue.

My specific case was an incorrect reference to SqlServerCe. See below. I had two projects referencing two different versions of SqlServerCe. I went to the project with the older version, removed the reference, then added the correct reference.

Target ResolveAssemblyReferences:
    Consider app.config remapping of assembly "System.Data.SqlServerCe, ..." 
        from Version "3.5.1.0" [H:\...\Debug\System.Data.SqlServerCe.dll] 
        to Version "9.0.242.0" [C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PublicAssemblies\System.Data.SqlServerCe.dll]
        to solve conflict and get rid of warning.
    C:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets : 
        warning MSB3247: Found conflicts between different versions of the same dependent assembly.

You do not have to open each assembly to determine the versions of referenced assemblies.

  • You can check the Properties of each Reference.
  • Open the project properties and check the versions of the References section.
  • Open the projects with a Text Editor.
  • Use .Net Reflector.

More Related Contents:

  1. Deciphering the .NET clr20r3 exception parameters P1..P10
  2. Why Large Object Heap and why do we care?
  3. A definitive guide to API-breaking changes in .NET
  4. LINQ on the .NET 2.0 Runtime
  5. What are the roots?
  6. Running MSBuild fails to read SDKToolsPath
  7. How do I detect at runtime that .NET version 4.5 is currently running your code?
  8. Path to MSBuild
  9. NAnt or MSBuild, which one to choose and when?
  10. How do the .NET Framework, CLR and Visual Studio version numbers relate to each other?
  11. How do I override CopyLocal (Private) setting for references in .NET from MSBUILD
  12. When is a method eligible to be inlined by the CLR?
  13. Running Code Analysis (FxCop > 10) on build agent without installing Visual Studio
  14. .NET 4.0 build issues on CI server
  15. When should copy-local be set to true and when should it not?
  16. Does the .NET CLR JIT compile every method, every time?
  17. msbuild, defining Conditional Compilation Symbols
  18. Equivalent of Class Loaders in .NET
  19. How to see JIT-Compiled code in .NET VM (CLR)
  20. How to call managed code from unmanaged code?
  21. Is it possible to get parameters’ values for each frame in call stack in .NET
  22. How can I auto increment the C# assembly version via our CI platform (Hudson)?
  23. No AppDomains in .NET Core! Why?
  24. Get Current .NET CLR version at runtime?
  25. How to conditionally deploy an app.config based on build configuration?
  26. Is the CLR a virtual machine?
  27. Found conflicts between different versions of the same dependent assembly that could not be resolved
  28. How to force a Solution file (SLN) to be opened in Visual Studio 2013?
  29. How do you databind to a System.Windows.Forms.Treeview control?
  30. XmlSerializer startup HUGE performance loss on 64bit systems

Leave a Comment