Team Development with Visual Studio Team Foundation Server

2. Click the Check-in Policy tab, click Add, and then select and configure the
appropriate policy.
Additional Resources
• For more information about creating and using a custom check-in policy, see “How
To – Step Through Creating Custom Check-in Policies for TFS” in this guide.
• To learn how to customize a check-in policy, see “Walkthrough: Customizing Checkin
Policies and Notes” at http://msdn2.microsoft.com/enus/library/ms181281(VS.80).aspx
• To see sample code that will disallow selected patterns on check-in, see “Checkin
Policy to Disallow Certain Patterns” at
http://blogs.msdn.com/jmanning/archive/2006/02/02/523125.aspx
• To see sample code that will enforce comments on check-in, see “Sample Checkin
Policy: Make Sure the Comment Isn’t Empty” at
http://blogs.msdn.com/jmanning/archive/2006/01/21/515858.aspx
• To learn how to register a new check-in policy, see “I’ve Made a New Check-In
Policy! How Do I Add It?” at
http://blogs.msdn.com/jmanning/archive/2006/02/07/526778.aspx
Detect When a Policy Has Been Overridden
Team Foundation Version Control does not prevent you from overriding a policy.
However, you can use the following steps to detect if a policy has been overridden:
• Use the Team Foundation Eventing Service (from the Team Foundation Core
Services API) for hooking into check-in events.
• Write a Notify method that parses the details of the changeset and then react to it if an
override has occurred.
Alternatively, you can manually scan changeset history to discover policy overrides.
Additional Resources
• To learn more about overriding a check-in policy, see “How to: Override a Check-in
Policy” at http://msdn2.microsoft.com/en-us/library/ms245460(VS.80).aspx
• To learn more about the Team Foundation Eventing Service, see “Eventing Service”
at http://msdn2.microsoft.com/en-us/library/bb130154(vs.80).aspx
• To learn how to receive an e-mail message when a policy has been violated, see
http://blogs.infosupport.com/marcelv/archive/2005/10/18/1635.aspx
Plan to Avoid Conflicts
Plan to avoid having multiple developers working in the same region of the same source
file at the same time. Do this to avoid conflicts that are potentially difficult to correctly
resolve. While automatic conflict resolution can resolve many conflicts, you should avoid
situations where two or more developers are working on the same method, or on the same