What are your favourite FxCop rules?

Question

Which FxCop rules do you most value? Which rules highlight the best .Net gotchas?

Answer 1

My favorite FxCop rules are the ones that don't give me errors when compiling my code.

Answer 2

Which FxCop rules do you most value?

The one I am going to write to stop developers from using #defines instead of configuration (Quote needed: Preprocessor usage is bad OO practice). And I like almost all of the design rules.

Answer 3

I find some of the usage and design rules particularly helpful. I can never remember the details of how to implement the IDisposable or ISerializable interfaces, so I appreciate the gentle reminders from rules like these:

• Implement IDisposable correctly
• Disposable fields should be disposed
• Call GC.SuppressFinalize correctly
• Implement ISerializable correctly
• Implement serialization constructors
• Mark ISerializable types with SerializableAttribute

Answer 4

The ones I value the most, and which highlight the gotchas, are the Performance rules.

Answer 5

This is not a FxCop rule but NDepend Code Query Language rule, but nevertheless, I love the CQL rule:

// <Name> Make sure refactored and added methods are covered by tests</Name>
WARN IF Count > 0 In SELECT METHODS WHERE 
PercentageCoverage < 100
AND (CodeWasChanged OR WasAdded)