Browse Source
Setting two or more FxCop rules to be flagged as errors instead of warnings was adding the rules into the CodeAnalysisRules element of the MSBuild project file with the semi-colon separators being escaped. This escaping then causes FxCopCmd.exe to fail.pull/35/head
1 changed files with 2 additions and 2 deletions
Loading…
Reference in new issue