Team Development with Visual Studio Team Foundation Server

Use Check-in Policies to Ensure That Developers Associate Work Items
with Check-ins
Set the Work Items check-in policy to force developers to associate their check-in with a
work item.
If a build breaks, it is important that you know what changesets are associated with the
build, and what work items those changesets are associated with, so that you can identify
the developer responsible for checking in this code and the area of the project on which
the developer is working.
To set the Work Items check-in policy to force developers to associate their check-in
with a work item
1. In Team Explorer, right-click your team project, select Team Project Settings, and
then click Source Control.
2. Click the Check-in Policy tab.
3. Click Add and then select and configure the Work Item check-in policy.
Additional Resources
• For more information about check-ins, see “How to: Check In Pending Changes” at
http://msdn2.microsoft.com/en-us/library/ms181411(VS.80).aspx
• For more information about work items and changesets, see “How to: Associate
Work Items with Changesets” at http://msdn2.microsoft.com/enus/library/ms181410(VS.80).aspx
Create Check-in Policies to Enforce Coding Standards
The project you are working on may require coding standards that are not covered by
static code analysis or by existing check-in policies. For example, your project may
require that your code never uses the tab character, or that all check-ins require
comments. You can create new check-in policies to cover these scenarios.
To enforce a code analysis check-in policy for a team project
1. In Team Explorer, right-click your team project, point to Team Project Settings, and
then click Source Control.
2. Click the Check-in Policy tab and then click Add.
3. In the Add Check-in Policy dialog box, select Code Analysis and then click OK.
4. In the Code Analysis Policy Editor, select either Enforce C/C++ Code Analysis
(/analyze) or Enforce Code Analysis For Managed Code. Select both if your
project contains a combination of managed and unmanaged code.
5. If you select managed code analysis, configure your required rule settings for
managed code analysis based on your required coding standards.
This determines precisely which rules are enforced.