I am getting "found conflict between different versions" from one of my projects.
How do I find out which assemblies are actually in conflict?
A:
Build the solution and check the output window - you should be able to see in there.
Michael
2010-04-10 09:17:40
I should be able to ... but I don't. (See my comment to @Jono).
ripper234
2010-04-10 10:16:40
A:
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
2010-04-10 09:22:44
It only shows a warning that doesn't specify which assemblies are conflicting.
ripper234
2010-04-10 10:16:11
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
2010-04-10 10:26:21
How about using msbuild.exe directly from the command line? <code>C:\Windows\Microsoft.NET\Framework\v4.0.30128\msbuild.exe MyTest.csproj</code>It might not be in the bit that's highlighted yellow, but scan the output for "No way to resolve conflict between..."
Jono
2010-04-11 19:10:41
A:
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.
KMan
2010-04-10 09:59:01
I was not the one who downvoted, but your answer does not seem relevant to my question.
ripper234
2010-04-10 13:24:52
@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
KMan
2010-04-11 09:58:35
I can confirm that when you get an "Unable to resolve conflict" message, double clicking in the output window does nothing.
Russ C
2010-08-05 08:55:38