I recently spent several days, and ultimately involved MS tech support, to figure out why I was getting warning MSB3247 ("Found conflicts between different versions of the same dependent assembly"). This warning happens when two or more assemblies in the same project reference different versions of a third assembly.
The warning tells me the name of the referenced assembly, but it doesn't give a clue as to the underlying cause of the problem (that is, it doesn't tell me which assemblies are referencing the different versions of the same assembly).
Ultimately, the tech support engineer and I had to resort to using ildasm to examine assembly manifests to figure out which assemblies in my project were causing the problem. This whole issue could have been avoided if the warning message had told me which assemblies were causing the problem in the first place.