Code Analysis Check-in Policies
When you use either Visual Studio Team Suite or Visual Studio Team System Development Edition, you can create a code analysis check-in policy. The code analysis check-in policy can be used to control and improve the quality of code that is checked into the code base.
The policy passes when the build is up to date and there are no code analysis errors. In addition, the rules enabled in the project are at least as restrictive as the rules that are defined in the check-in policy.
.gif "Important note") Important Note: |
|---|
To use check-in policies, you must be connected to Team Foundation Server. |
For information about check-in policy failures, see Code Analysis Policy Errors.
In This Section
Describes how to create custom check-in policies associated with Team Foundation version control check-ins. |
|
Explains the procedures that are used to modify a check-in policy. |
|
Explains the procedure that is used to migrate code analysis policy from the server to the client. |
|
Describes the steps that are required to delete a check-in policy. |
|
Explains the steps that are used to either enable or disable an existing check-in policy. |
|
Describes the steps that are used to configure custom check-in notes associated with Team Foundation version control check-ins. |
|
Lists the code analysis related policy errors that can cause a check-in to fail. |
|
Explains check-in compatibility issues between versions of Visual Studio Team System. |
|
How to: Enforce Maintainable Code with Code Analysis Check-in Policy |
Explains how to use Code Analysis with check-in policy to verify and enforce the compliance of code to Code Metrics standards. |
Related Sections
How to: Connect to Team Foundation Server