I've come across the following situation, and wonder if anyone else has had this problem or can offer a workaround.
In order to have my projects be able to refer to a required external assembly both by assembly name and by project name (if it is loaded in the same solution), I added a element to the .csproj file. In one branch, the assembly is loaded from disk as a binary reference, and in the other it is loaded via a project reference.
This appears to trip up ReSharper, since the same reference appears twice in the project file, even though there is logic which makes this valid in MsBuild.
The result is that MSBuild compiles the project successfully, and Resharper complains of ambiguous references.
Is there any way I can get Resharper to observe the ]]> element and its consequences?