Team Development with Visual Studio Team Foundation Server

Additional Resources
• For more information about removing permissions, see “How to: Remove Access to
Source Control Files” at http://msdn2.microsoft.com/enus/library/ms400718(VS.80).aspx
Branch/Label/Merge
• When should I use labels?
• How do TFS labels differ from VSS labels?
• What is branching?
• When should I consider branching?
• What are the reasons not to branch?
• How do I use branching to release my application?
• How do I use branching to maintain my application?
• How do I use branching to reduce conflicts between teams?
• How do I use branching to reduce conflicts between features?
• What are the proven practices for branching and merging?
• What is the difference between branching and labeling?
• What is the "path space" branching model?
• How does the TFS promotion model work?
• How do I merge two branches?
• Can I merge across team projects?
• What is a baseless merge?
• What is the code promotion model?
• What is the difference between the logical and physical view of branches?
• If I use the code promotion model, how often should I merge?
When should I use labels?
Use labels to group a set of files and folders together for future operations. You can use
labels for branching, merging, diffing, or getting files. A label provides a marker to which
you can return when performing one of the above operations at a later date.
Team Foundation Build automatically labels the file versions associated with each build
that it creates.
Note: If you are unsure whether or not you need a branch, you can label a set of files and
later create a branch based on this label.
Additional Resources
• For more information about labels, see “Working with labels” at
http://msdn2.microsoft.com/en-us/library/ms181439(VS.80).aspx
• For further information about labels, see “How to: Apply Labels” at
http://msdn2.microsoft.com/en-us/library/ms181440(VS.80).aspx