Rule Topics


This section provides in-depth discussions and examples for the FxCop rules. The information shown in the following table is provided in the rule topics.





The TypeName for the rule.


The unique identifier for the rule.


The category of the rule.

Message Level

The importance of the issue identified by the rule.


The estimate of the probability that the issue is detected correctly. This value is an integer between 1 and 99.

Breaking Change

Whether the fix for a violation of the rule constitutes a breaking change. Breaking change means that an assembly that has a dependency on the target that caused the violation will not re-compile with the new fixed version or might fail at runtime due to the change. When multiple fixes are available and at least one fix is a breaking change and one fix is not, both 'Breaking' and 'NonBreaking' are specified.


The specific managed code that causes the rule to generate a message.


Discusses the issues behind the rule.

How to Fix Violations

Explains how to change the source code to satisfy the rule and prevent it from generating a message.

When to Exclude Messages

Describes when it is safe to exclude a message from the rule.

Example Code

Examples that violate the rule and "fixed" examples that satisfy the rule.

Related Rules

Related rule topics.

See Also

Related topics from the Microsoft® .NET Framework Design Guidelines and the .NET Framework SDK.


In This Section

Design Rules

Rules that support proper library design as specified by the .NET Framework Design Guidelines.

Globalization Rules

Rules that support world-ready libraries and applications.

Interoperability Rules

Rules that support interacting with COM clients.

Mobility Rules

Rules that support efficient power usage.

Naming Rules

Rules that support adherence to the naming conventions of the .NET Framework Design Guidelines.

Performance Rules

Rules that support i high performance libraries and applications.

Portability Rules

Rules that support portability across different platforms.

Security Rules

Rules that support safer libraries and applications.

Usage Rules

Rules that support proper usage of the .NET Framework.

Contact the FxCop team.

© 2002 - 2004 Microsoft Corporation. All rights reserved.