Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Note: the <a href="https://blogs.msdn.microsoft.com/visualstudioalmrangers/2015/04/22/library-of-tooling-and-guidance-solutions-aka-msvsarsolutions/" rel="nofollow noreferrer">Version Control (ex Branching and Merging) Guide</a> can help here.</p> <p>In the "Single Dev Team Scenario 2.0.pdf" document of <a href="http://tfsbranchingguideii.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=20785#DownloadId=52465" rel="nofollow noreferrer">TFS Branching Guide - Lab.zip</a> file, you will see that the creation of a branch is followed by a commit (a checking of all files from the original branch.<br> The space used is minimized, as described in <a href="http://branchingguidance.codeplex.com/wikipage?title=Isolation%20for%20Collaboration&amp;referringTitle=Home" rel="nofollow noreferrer">Isolation for Collaboration</a> page:</p> <blockquote> <p>When you create a new branch and commit, all of the files in the new branch that are identical to the files in the source branch point to the same content.<br> The result is that a branch consumes very little additional storage space, and that storage space expands only when the branched file becomes different than the source.<br> And even when files change, Team Foundation Server employs a differencing engine to analyze changes between files and once again optimize storage space.</p> </blockquote> <p>So it is heavy branching for TFS2008 (with space optimization).</p> <p>In TFS2010, branches are first class object and easily separated from simple folders.</p> <p><img src="https://i.stack.imgur.com/S84ah.jpg" alt="TFS branches"></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload