Team Development with Visual Studio Team Foundation Server

Modify the Paths to Solutions in the TFSBuild.proj Files, When Creating
a Complete Branch
When you create a new branch, including the Team Build Types, the paths in the build
types still point to the previous location. In order for the build to work on the new branch,
you must update the paths in the build type project files so that they reference the new
path locations created after the branching operation.
When you create a full branch, you also branch the build types. The build types contain
references to folders from the original source control tree. To have these build types refer
to the branch folders, you must edit the folder references in these files.
To perform the update, check out the build types from the branch you want to modify,
apply the updates, and then commit the changes to the branch.
Additional Resources
• For more information about how to update your build types, see “How to: Update
Build Types on Branched Team Projects” at http://msdn2.microsoft.com/enus/library/ms252500(VS.80).aspx
Check-in Policies
• Use check-in policies to improve check-in quality.
• Use check-in policies to associate work items with the build.
Use Check-in Policies to Improve Check-in Quality
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.
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 “Check-in
Policy to Disallow Certain Patterns” at
http://blogs.msdn.com/jmanning/archive/2006/02/02/523125.aspx