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.

• 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 />

How to Perform a Merge<br />

Use the merge command to integrate changes from one branch into another. To perform<br />

a merge, you can use the merge functionality in Source Control Explorer, or you can use<br />

the tf merge command line. You can merge by changeset, label, date, or version. To start<br />

a merge, right-click the branch in Source Control Explorer and then click Merge. The<br />

Source Control Merge Wizard allows you to choose the target branch <strong>with</strong> which to<br />

merge.<br />

Depending on your branch structure, you might need to merge changes up the branch<br />

hierarchy, down the hierarchy, or across the hierarchy. If you are merging across the<br />

hierarchy, you are performing a baseless merge and you must use the tf merge command<br />

line, because you cannot do this <strong>with</strong> <strong>Visual</strong> <strong>Studio</strong>. A baseless merge allows you to<br />

merge files and folders that do not have a branch/merge relationship. After a baseless<br />

merge, a merge relationship exists and future merges are not baseless. You still need to<br />

execute the merges from the command line, but the number of merge conflicts will be<br />

reduced.<br />

Keep the following in mind when performing merges:<br />

• Merging along the hierarchy—from parent to child or from child to parent—<br />

results in fewer conflicts than merging across the hierarchy.<br />

• The branch hierarchy is based on the branch parent and branch child, which might<br />

be different from the physical structure of what you see in Source Control<br />

Explorer; for example:<br />

o Physical structure:<br />

• <strong>Development</strong> –<strong>Development</strong> branch<br />

• Main – Integration branch<br />

• Releases – Container for release branches<br />

• Release 1 – Release Branch<br />

o Logical structure:<br />

• Main<br />

• <strong>Development</strong><br />

• Release 1<br />

Additional Resources<br />

• For more information about merging, see “Understanding Merging” at<br />

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

• For a walkthrough describing how to perform a merge, see “How to: Merge Files and<br />

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

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

Saved successfully!

Ooh no, something went wrong!