Slimming down the FxCop rule set

I asked a group of consultants currently working in my office for advice on which FxCop rules were actually applicable to our environment.  One particularly useful piece of advice was to consider whether or not unknown people or applications would be using what I’d written.  It allowed me to disable the following rules:

  • Mark assemblies with CLSCompliant.  Since there won’t be any third-party users of the assemblies I ran FxCop on, that rule can go away.
  • Mark assemblies with ComVisible.  The same argument as above applies to this rule.
  • Assemblies should have valid strong names.  Once we get certificates, we would reactivate this rule.

I’ll revisit the list periodically to make changes as I improve my understanding.