Comments on: Find Conflicting Assembly References

By: Chad

Chad — Fri, 25 Jun 2010 16:32:53 +0000

Wow, I’ve just spent 2 hours trying to find this one rogue reference and this tool just found it for me in 5 seconds. Much thanks!

By: Brian

Brian — Mon, 31 May 2010 04:10:53 +0000

@Rene: the Output window tells you which assembly is conflicted (which is often enough) but doesn’t tell you which assemblies are causing the conflict.

@Felix: perhaps the problem is 2 levels deep. This test only looks at immediate references and not references of references (e.g. your project -> A.dll -> B.dll -> mscorlib 1.0.5000.0). You’ll need to make GetReferencesFromAllAssemblies() a little smarter to find these problems.

By: Felix Collins

Felix Collins — Sun, 30 May 2010 23:18:49 +0000

Problem 1
I find that this picks up mscorlib 2.0.0.0 and 1.0.5000.0 for most of my projects. Why would this be? As far as I can see the project file does not specify which mscorlib to use. I check all the projects in the solution using coolcommands ref manager and they all report mscorlib 2.0.0.0. I suppose some of the third party libs I reference could have been built to reference mscorlib 1.0.5000.0.

Problem 2
I get a build warning for different versions of DirectShowLib. But the test does not show this up. This is caused by a third party lib referencing the older version.

“Consider app.config remapping of assembly “DirectShowLib-2005, from Version “2.0.0.0″ [] to Version “2.1.0.0″ to solve conflict and get rid of warning.” (edited for clarity)

By: Rene Schulte

Rene Schulte — Thu, 22 Apr 2010 11:41:41 +0000

Or just look at the Output window after the build.

By: Steffen S

Steffen S — Wed, 17 Feb 2010 15:56:58 +0000

Thanks that helped! Nice to have around.

By: Tim Coulter

Tim Coulter — Tue, 09 Feb 2010 13:26:49 +0000

Many thanks for this Brian – it was a timely and effective solution for an irritating problem.