The current version of the FxCop package is not very configurable. Some of
the rules enforced by the default FxCop configuration may not be
appropriate or desired for some projects (or for certain assemblies in a
project), running FxCop with the default FxCop configuration on such a
project may result in thousands of (irrelevant) rule violations. In such
cases, the FxCop package's reports are useless as a source of "quick
feedback", and are only useful if someone takes a significant amount of
time to analyze the output and try to find the important violations
scattered among the much larger number of false positive violations.
Therefore, it would be extremely useful if the FxCop package supported the
following configuration functionality:
1. Supported the (optional) use of an FxCop project file (and therefore
supported all standard FxCop configuration functionality that such a
project file enables).
2. Supported some optional package configuration (e.g. via optional
package properties) that would allow for some level of FxCop configuration
customization (with or without the use of a FxCop project file) via the
build scripts. For example, one might want to configure the package so
that a "dev" build would report only Error-level violations, while
a "Release" build would report all violations.
Original issue reported on code.google.com by justin.w...@gmail.com on 16 Mar 2009 at 8:51
Original issue reported on code.google.com by
justin.w...@gmail.comon 16 Mar 2009 at 8:51