Team Development with Visual Studio Team Foundation Server

• For more information about branching, see “How to: Branch Files and Folders” at
http://msdn2.microsoft.com/en-us/library/ms181425(VS.80).aspx
• For more information about merging, see “How to: Merge Files and Folders” at
http://msdn2.microsoft.com/en-us/library/ms181428(VS.80).aspx
• For additional descriptions of how to branch and merge in Visual Studio 2005, see
“Branching and Merging Team Foundation Source Control” at
http://msdn2.microsoft.com/en-us/library/ms181423(VS.80).aspx
Use Check-in Policies to Improve Check-in Quality
You should use a combination of code analysis and testing policies to improve check-in
quality. For example, use the supplied testing policy to ensure that specific tests are
executed and passed prior to allowing source to be checked into TFS source control. You
can also configure a code analysis policy to help ensure that your code meets certain
quality standards by ensuring that security, performance, portability, maintainability, and
reliability rules are passed.
By enforcing this type of check-in policy in addition to policies that enforce coding
standards and guidelines, you can test your code against specific code quality issues.
To enforce a code analysis check-in policy for a team project, you right-click your team
project in Team Explorer, point to Team Project Settings, and then click Source
Control. 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
Use Build Notification Alerts to Learn When the Build Has Completed
To keep track of your build process, you can create alerts that send e-mail messages to
you or to others when a build has completed.