![]() ![]() ![]() Instead turn it to Diagnostic (from Tools->Options->Project and Solutions->Build and Run, set MSBuild project build output verbosity), whereupon you'll see messages such as: This is incorrect (or at least it was for some versions of Visual Studio - it seems to be OK on an up to date VS2015 Update 3 or later). These reference conflicts are listed in the build log when log verbosity is set to detailed. ![]() On VS2013.2, to actually trigger the emission of the cited information, you need to not read the message, which says:Ĭ:\Program Files (x86)\MSBuild\12.0\bin\(1697,5): warning MSB3277: Found conflicts between different versions of the same dependent assembly that could not be resolved. While the other responses say this, they don't make it explicit, so I will. Eta: There's a killer article on this stuff by SO's own Craver that you should read ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |