Team Development with Visual Studio Team Foundation Server

This is important because it provides quick turnaround among teams. For example, if the
test team is notified by e-mail of a completed build, they can start their test pass without
having to wait for manual instructions.
Additional Resources
• For more information about build notifications, see “How to: Receive Build
Notification E-Mail” at http://msdn2.microsoft.com/enus/library/ms181725(VS.80).aspx
• For further information about build notifications, see “How to: Add or Edit Alerts” at
http://msdn2.microsoft.com/en-us/library/ms181335(VS.80).aspx
Branching
• Use new Team Build Types when creating a partial branch.
• Modify the paths to solutions in the TFSBuild.proj files, when creating a
complete branch.
Use New Team Build Types When Creating a Partial Branch
When you create a branch that contains a subset of the solutions in your team project, you
might need to create new build types in order to build successfully.
There are two types of partial branches:
1. A partial branch that does not include branching of any build types. This would
occur within a team project, and would simply branch solution and source files but
would not branch any of the TeamBuildTypes folders into new folders.
2. A partial branch that includes branching of build types. This would occur within
a team project, and would branch some of the TeamBuildTypes subfolders (that is,
build types) in addition to other folders containing the relevant solution and source
files.
If you create a partial branch that does not include Team Build Types all of the existing
Team Builds will continue to work, but you will need to create a new Team Build Type if
you want to build the branch. Create new build types by using the Team Build Wizard in
order to build the code in the new branch. These new build types will point to the new
branch location and may also point to the parent location for any solutions that must be
included in the build but that were not branched.
If you create a partial branch that includes Team Build Types, the build types that are
copied over with the branch will point to the original, parent branch locations and
therefore will not allow you to build the new branch. Modify the branched build types so
that they point to the new branched code locations.
Additional Resources
• For more information about how to update your build type, see “How to: Update
Build Types on Branched Team Projects” at http://msdn2.microsoft.com/enus/library/ms252500(VS.80).aspx