Code Contracts and conflicting satellite assemblies

Code Contracts : Conflicting assemblies

I've found that the code contracts compiler is a bit on the sensitive side. 

We recently resolved an issue with the code contracts compiler not being able to locate satellite assemblies.

The problem

We recursively build up the search path in MSBuild so that the CC compiler can resolve satellite assemblies, but in the case of of two assemblies having the same name, the CC compiler still throws up an error relating to a conflicting assembly.

The solution

At the moment, our solution is to rename or remove the conflicting assembly from the search path.