Here's an interesting blog article<http://blogs.msdn.com/codeanalysis/archive/2007/08/09/what-rules-do-microsoft-have-turned-on-internally.aspx>about how Microsoft applies the FxCop rules to some of their own internal projects.
I read it a few years ago now, so not sure how current it still is, but it might give you a push in the right direction as to deciding which rules are useful and which rules are just too painful. Joe. On Fri, Apr 23, 2010 at 8:49 AM, Greg Keogh <[email protected]> wrote: > Searches on this subject are completely confusing. I cannot yet find a > definitive and clear description of how to create FxCop custom dictionary > files. > > > > My solution has dozens of project files, grouped by subsystem of the app. I > have an FxCop file for each subsystem and I want a custom dictionary for > each one. Can someone point me to clear instructions on this matter? > > > > NOTE -- I’m returning to using FxCop in anger over the last week. After not > using it for over a year, I can tell you that it’s cruel and unforgiving and > points out how undisciplined you can be. Old habits like catch > (Exception)returned and I had stale code, methods that could be static, > incompletely > implemented serializable classes and sloppy naming. David K will be pleased > to know that it did in fact find my “bug” from last week where I forgot to > SuppressFinalize in some classes. I highly recommend that anyone starting > new projects should run FxCop as a part of their development process, it > stops bad coding habits, teaches you some tricks and enforces standards. > > > > Some of the FxCop rules are really painful and repetitive and solving them > risks making your code more dense unless you jump through small hoops. I > plan to ask about them over the coming weeks and see how other people deal > with them. > > > > Thanks > > Greg >
