13

I am getting "found conflict between different versions" from one of my projects.

How do I find out which assemblies are actually in conflict?

ripper234
  • 222,824
  • 274
  • 634
  • 905
  • Are you seeing something like this: 103>C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1360,9): warning MSB3247: Found conflicts between different versions of the same dependent assembly. – GregC Apr 05 '11 at 18:12
  • [http://stackoverflow.com/questions/1871073/resolving-msb3247-found-conflicts-between-different-versions-of-the-same-depend](http://stackoverflow.com/questions/1871073/resolving-msb3247-found-conflicts-between-different-versions-of-the-same-depend) – GregC Apr 05 '11 at 18:14

3 Answers3

1

Build the solution and check the output window - you should be able to see in there.

Mike
  • 6,149
  • 5
  • 34
  • 45
  • 3
    I should be able to ... but I don't. (See my comment to @Jono). – ripper234 Apr 10 '10 at 10:16
  • 1
    see http://stackoverflow.com/questions/1871073/resolving-msb3247-found-conflicts-between-different-versions-of-the-same-depend as noted above – twomm Jul 02 '13 at 10:11
  • Check your CSPROJ files. I didn't see any addt'l info in the output window, but I did see an incorrect reference path in the CSPROJ that I was seemingly unable to remove via the VS GUI. Removed, reloaded, and rebuilt w/o issue. – Sanjay Uttam Dec 06 '13 at 20:56
0

The error list window (CTRL+W,E) should show which assemblies were in conflict. Failing that, the output window (CTRL+W,O) will show which of the conflicting assemblies was arbitrarily picked for the build.

Jono
  • 1,964
  • 4
  • 18
  • 35
  • 4
    It only shows a warning that doesn't specify which assemblies are conflicting. – ripper234 Apr 10 '10 at 10:16
  • To use a phrase I coined a while back, "it works on my machine." Are you using the RC version of VS2010? And is it a C# project? – Jono Apr 10 '10 at 10:26
  • Yes I'm sure, RC version, and native C# project. – ripper234 Apr 11 '10 at 11:22
  • How about using msbuild.exe directly from the command line? C:\Windows\Microsoft.NET\Framework\v4.0.30128\msbuild.exe MyTest.csproj It might not be in the bit that's highlighted yellow, but scan the output for "No way to resolve conflict between..." – Jono Apr 11 '10 at 19:10
  • 1
    see http://stackoverflow.com/questions/1871073/resolving-msb3247-found-conflicts-between-different-versions-of-the-same-depend as noted above – twomm Jul 02 '13 at 10:10
-1

alt text http://img82.imageshack.us/img82/2484/vs2010sucks2.png

Usually, double clicking the error takes you to the line causing problems. There you can check the method calls being called from referencing assemblies.

--Edit-- But, I agree with the last comment; link error does not throw on the particular line of code.

KMån
  • 9,896
  • 2
  • 31
  • 41
  • @Downvoter: Any reasons for the downvote you might like to add? – KMån Apr 10 '10 at 10:36
  • I was not the one who downvoted, but your answer does not seem relevant to my question. – ripper234 Apr 10 '10 at 13:24
  • @Ripper234: `How do I find out which assemblies are actually in conflict?` Usually when you double click the error line in the output window, the IDE takes you to line causing the error. The intention of this post was to help you get to that line and see the conflicting assemblies. Also see, http://social.msdn.microsoft.com/Forums/en-US/netfxcompact/thread/73d1b418-0b2d-4649-b491-21b39a468457 – KMån Apr 11 '10 at 09:58
  • 3
    I can confirm that when you get an "Unable to resolve conflict" message, double clicking in the output window does nothing. – Russ Clarke Aug 05 '10 at 08:55
  • 2
    Output window is simply a text dump... how could clicking that possible do anything other then select some text??? – Dave Lawrence May 17 '13 at 10:54
  • In many cases, this error gives you a link within Microsoft.Common.Targets, instead of the actual assembly in conflict. – Bill Yang May 22 '13 at 17:20
  • 1
    @daveL VS is really quite smart, try it out – twomm Jul 02 '13 at 10:13