26.04.2015 Views

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

o Shared Code – container for source code that is shared from other projects<br />

o Unit Tests – container for unit tests<br />

o Lib – container for binary dependencies<br />

• Docs – container for documentation that will ship <strong>with</strong> the product<br />

• Installer – container for installer source code and binaries<br />

• Tests – container for test team test cases<br />

Branch at the level of the Source folder to ensure that the new branch contains all source<br />

and configuration files.<br />

Additional Resources<br />

• For an introduction to branching and merging, see “Branching and Merging Primer”<br />

at http://msdn2.microsoft.com/en-us/library/aa730834(VS.80).aspx<br />

• For more information about branching, see “How to: Branch Files and Folders” at<br />

http://msdn2.microsoft.com/en-us/library/ms181425(VS.80).aspx<br />

• For more information about merging, see “How to: Merge Files and Folders” at<br />

http://msdn2.microsoft.com/en-us/library/ms181428(VS.80).aspx<br />

• For additional descriptions of how to branch and merge in <strong>Visual</strong> <strong>Studio</strong> 2005, see<br />

“Branching and Merging <strong>Team</strong> <strong>Foundation</strong> Source Control” at<br />

http://msdn2.microsoft.com/en-us/library/ms181423(VS.80).aspx<br />

Do Not Branch Too Deeply<br />

Do not branch too deeply because this will add to the time required to merge a change<br />

from a child branch up to the topmost parent. For example, in the following branching<br />

structure:<br />

• <strong>Development</strong> – Container for development branches<br />

o <strong>Development</strong> Branch<br />

• Sub-Branch<br />

• Sub-Sub-Branch<br />

• Main – Integration Branch<br />

o Source<br />

o Other Asset Folders<br />

Merges result in fewer conflicts when performed along the branch hierarchy. Therefore,<br />

if there is a change in the Sub-Sub-Branch that you would like to merge into Main, you<br />

would first need to merge <strong>with</strong> the Sub-Branch and the <strong>Development</strong> Branch before<br />

you can merge into Main. Each merge takes time to complete, resolve conflicts, build,<br />

and test, which multiplies merge time by the level of branches you have created in your<br />

branch structure.<br />

Additional Resources<br />

• For an introduction to branching and merging, see “Branching and Merging Primer”<br />

at http://msdn2.microsoft.com/en-us/library/aa730834(VS.80).aspx

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!