Please note that FxCop is very customizable regarding the rules you want to apply. You may find that it works best by gradually introducing it; only for a specific set of rules for a specific set of files or initially excluding all obsolete files.
There are mandatory rules that you can never activate, because they simply do not fit your problem domain. And remember that if a piece of code "breaks the rule" for a specific purpose, there is an attribute for marking such code as acceptable, although I would set a rule that all such overrides should use the Justification property for the attribute to indicate why.
Finally, since the built-in rules will greatly help in improving the quality of the code, really big wins must be achieved in user rules that will allow you to check corporate agreements. If you do not automate peer review in this way, then you cannot really guarantee compliance.
I use FxCop as an integrated part of the build system at work, and our shared libraries are currently released with all the rules included with minimal attribute overrides, and this has been useful in more than a few places.
jerryjvl
source share