CODEWITHSUNDEEP
code-analysisfxcoprules
Maxime Rouiller
Maxime Rouiller

Reputation: 13699

Which rule from FxCop do you deactivate?

I personally don't use FxCop yet. We want to work out the unit testing first before going with code analysis. However, which rules would you permanantly deactivate? Which rules would you deactivate temporarily and in which situation?

Upvotes: 4

Views: 1080

Answers (5)

Wim Coenen
Wim Coenen

Reputation: 66753

CA2210 Assemblies should have valid strong names is an annoying one.

Upvotes: 3

Timothy Khouri
Timothy Khouri

Reputation: 31865

It complains about "ID" and suggests "Id"... even though that follows the "two-character-abbreviations-are-all-capped" rule :O)

Upvotes: 0

DOK
DOK

Reputation: 32851

I don't use the naming convention rule that prohibits underscores in method/event names. I've gotten used to "Button1_Click". Visual Studio automatically inserts the underscores, so you have to manually remove them. I just think it's easier to leave them alone. And, I add the underscore when I create a method/event.

Upvotes: 2

JaredPar
JaredPar

Reputation: 755259

I dislike rule CA1021: Avoid out parameters. Out parameters are useful for many different patterns (including the .Net Try* pattern). Out can certainly be overused but really it seems overkill to have an FxCop rule for it.

Rule CA1021

Upvotes: 5

Quibblesome
Quibblesome

Reputation: 25429

There's a whole list of pedantic crap you'll want to turn off depending on the system you're building. I'd suggest examining the FxCop output and deciding yourself. One mans pedantry is anothers "must have".

Upvotes: 2

Related Questions