Browse Source

Fix FxCop failing to find rules defined in project.

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
Matt Ward 13 years ago
parent
commit
768a0c81aa
  1. 4
      src/AddIns/Analysis/CodeAnalysis/Src/AnalysisProjectOptionsPanel.xaml.cs

4
src/AddIns/Analysis/CodeAnalysis/Src/AnalysisProjectOptionsPanel.xaml.cs

@ -41,12 +41,12 @@ namespace ICSharpCode.CodeAnalysis @@ -41,12 +41,12 @@ namespace ICSharpCode.CodeAnalysis
}
public ProjectProperty<string> CodeAnalysisRuleAssemblies {
get { return GetProperty("CodeAnalysisRuleAssemblies","",TextBoxEditMode.EditEvaluatedProperty); }
get { return GetProperty("CodeAnalysisRuleAssemblies", "", TextBoxEditMode.EditEvaluatedProperty); }
}
public ProjectProperty<string> CodeAnalysisRules {
get { return GetProperty("CodeAnalysisRules","",TextBoxEditMode.EditEvaluatedProperty); }
get { return GetProperty("CodeAnalysisRules", "", TextBoxEditMode.EditRawProperty); }
}
#region Rule Assemblies Property

Loading…
Cancel
Save