ProjectReference with Condition in your MSBuild project files
Since some time I have the current scenario where I need to have conditional reference in a project. Basically the application must reference an assembly in one case in other it should reference another one. This was working correctly from an MSBuild point of view as the first implemented solution let me compile and run the application on my development machine and it was also working for our TeamCity build server. So everything was fine in this perfect word expect one thing!
The issue was the following; Visual Studio was showing two references of the ‘same assembly’ with different path. Not really an issue you would say because the correct one was used at compile time and at run time in all configurations. So the issue was that this had an impact of ReSharper. And this is I cannot accept because it affect my productivity.
So the other day I had a discussion with Ilya of JetBrains which gave me some idea but also told me that ReSharper reads project structure out of Visual Studio and that it doesn’t provide lots of info, e.g. conditions on references. So this is why seeing two reference of the ‘same assembly’ was not a problem on Visual Studio itself and on the build server but was an issue to ReSharper because it was seeing two same reference, same namespace, same classes…
Today I had some time free and decided to see where I can come with this issue. And I found a solution.
My first solution, which had the explained issue was the same as the one on this post “Don’t be afraid of your csproj-Files (III): We have a condition”, so having a Condition on the ItemGroup.
The solution I came to is to bring the Condition to one upper level than the ItemGroup, so I used **Choose **like this:
Reloading the project I had the surprise to see only one reference and that ReSharper was working again correctly!
For sure the build on TeamCity is also working perfectly.