Customized MsBuild file causes ReSharper parsing to fail Follow

Hello codekaizen,

ReSharper doesn't parse MSBuild files by itself, it uses the information
about project reference provided by Visual Studio
at runtime. So my guess is that it might be a Visual Studio problem. Please
post a sample customized build file here, so that
we can investigate further.

Thanks.


Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Greetings,

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 <Choose> 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 <Choose> element
and its consequences?

Thanks Dmitry,

I see. I'll have to come up with some test case for this, as it looks like you are correct.