@Microsoft: please provide universal and professional concepts
A note on machine- and edition-specific Code Analysis paths added to Visual Studio project files and the problems they cause for portable projects, mixed-edition teams, and continuous integration builds.
Why such constructs are included in the .csproj-Files?
<CodeAnalysisRuleSetDirectories>;c:\Program Files (x86)\Microsoft Visual Studio 10.0\Team Tools\Static Analysis Tools\\Rule Sets</CodeAnalysisRuleSetDirectories>
<CodeAnalysisRuleDirectories>;c:\Program Files (x86)\Microsoft Visual Studio 10.0\Team Tools\Static Analysis Tools\FxCop\\Rules</CodeAnalysisRuleDirectories>
So it every projects needs some manual steps to clean the project file so the solution could be build on a continuous integration server. That annoying!
And also in a Visual Studio mixed editions team that’s too specific for the ultimate edition.
As good as Visual Studio in most cases is, sometimes it is really far away from professional coding fundamentals and best practices. ☹️