Project-level settings for custom diagnostics?

Topics: General
Apr 10, 2014 at 3:06 PM
Are there already mechanisms in place for configuring the following for custom diagnostics at a project level:
  1. Treating all diagnostic warnings as errors? (Neither TreatWarningsAsErrors nor CodeAnalysisTreatWarningsAsErrors seem to have any effect on this.)
  2. Disabling specific diagnostics?
If so, what might these mechanisms be? If not, are they planned?
Apr 10, 2014 at 8:46 PM
We are thinking about using ruleset files similar to how VS codeanalysis issues are configurable. The compilers now take two switches - /a:foo.dll to take a list of custom diagnostic analyzers and /ruleset:foo.ruleset which can specify whether specific diagnostic IDs are enabled\disabled or if they should be treates as warnings or errors etc.
Apr 12, 2014 at 8:26 PM
Excellent! Are you planning on supporting allowing exactly the same ruleset file to be used to specify Roslyn and FxCop options for a project? This would be much more convenient for users than the alternative, although it would require both stacks to strictly adhere to exactly the same schema.
Apr 12, 2014 at 8:53 PM
Yes that's the goal.
Apr 13, 2014 at 3:22 AM