However, its’ too darn strict. We’ve been using it for the past couple of months and we never really managed to pass it perfectly.

Morevoer, I just find it ironic that Microsoft Components themselves cannot pass FxCop.

A bit late to the party I know - but I couldn’t let that rest… FxCop specifically says (in help files and throughout) that it is only a guide and that you should build up it’s custom dictionaries/rule exceptions to ensure false positives (I’m guessing you don’t have copies of MS’s settings).

Secondly Fx Cop was developed alongside the Framework and as such many sections of the framework were developed without access to FxCop others worked to older, unrevised versions (and guess what; FxCop is still being revised).

Lastly, forgetting the fact that there may be good reasons for the violations that FxCop reports, - can you imagine the complaints if MS actually ‘fixed’ some of them and thus broke hundreds of applications?

That was bit long and probably unecessary - but I had somebody saying the exact same thing to me the other day… so it was on my mind