1

Analyze New Code

• If the new code is managed code, run Code Analysis for Managed Code to identify rule violations and warnings. If the existing code is native code, run Code Analysis for C/C++ to identify rule violations and warnings.
• Fix any rule violations or warnings, then build, and run unit tests. If any changes break a unit test, debug and fix the code so the unit test runs successfully.
• Fix one rule violation or warning at a time. Repeat until all of the rules are checked or all warnings are gone.

2

Analyze Existing Code

• For existing code bases with a large number of warnings, consult the code analysis guidelines for a baseline of rules and warnings established for existing code. The baseline may indicate a category of rules or warnings that is to be eliminated. If automation is used, determine the number of warnings in the existing code base.
• If the existing code is managed code, run Code Analysis for Managed Code to identify rule violations and warnings. If the existing code is native code, run Code Analysis for C/C++ to identify rule violations and warnings.
• Fix any rule violations or warnings, then build, and run unit tests. If any changes break a unit test, debug and fix the code so the unit test runs successfully.
• Fix one rule violation or warning at a time. Repeat until the code conforms to the established code analysis baseline.

The code is analyzed and is within established guidelines for code analysis.