Which FxCop rule do you deactivate?

Question

I personally have not used FxCop yet. First, we want to test the device first before going with code analysis. However, what rules would you constantly deactivate? What rules would you temporarily disable and in what situation?

Answer 1

I do not use a naming convention rule that prohibits underscores in method / event names. I'm used to Button1_Click. Visual Studio automatically inserts underscores, so you must manually remove them. It’s just easier for me to leave them alone. And I add underline when I create a method / event.

Answer 2

I don't like rule CA1021: Avoid options. Output options are useful for many different templates (including the .Net Try * template). The conclusion can certainly be excessive, but it actually seems redundant to have an FxCop rule for it.

Rule CA1021

Answer 3

CA2210 Assemblies must have valid strong names , this is annoying.

Answer 4

There is a whole list of pedantic crap that you want to turn off depending on the system you are building. I would suggest exploring the output of FxCop and decide. One man of pedantry is someone else's "must be."

Answer 5

He complains about "ID" and suggests "Id" ... although this follows the rule "two characters, abbreviations - all this": O)