Code Analysis for Managed Code Warnings
The Managed Code Analysis tool provides warnings that indicate rule violations in managed code libraries. The warnings are organized into rule areas such as design, localization, performance, security, and so forth. Each warning signifies a violation of a Managed Code Analysis rule. This section provides in-depth discussions and examples for each Managed Code Analysis warning.
The following table shows the type of information provided for each warning:
The TypeName for the rule.
The unique identifier for the rule. CheckId and Category are used for in-source suppression of a warning.
The category of the warning.
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 run time because of the change. When multiple fixes are available and at least one fix is a breaking change and one fix is not, both 'Breaking' and 'Non Breaking' are specified.
The specific managed code that causes the rule to generate a warning.
Discusses the issues behind the warning.
How to Fix Violations
Explains how to change the source code to satisfy the rule and prevent it from generating a warning.
When to Suppress Warnings
Describes when it is safe to suppress a warning from the rule.
Examples that violate the rule and corrected examples that satisfy the rule.
Warnings that support correct library design as specified by the .NET Framework Design Guidelines.
Warnings that support world-ready libraries and applications.
Warnings that support interacting with COM clients.
Warnings that support library and application maintenance.
Warnings that support efficient power usage.
Warnings that support adherence to the naming conventions of the .NET Framework Design Guidelines.
Warnings that support high performance libraries and applications.
Warnings that support Portability across different platforms.
Warnings that support library and application reliability, such as correct memory and thread usage.
Warnings that support safer libraries and applications.
Warnings that support appropriate usage of the .NET Framework.