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.

To consume the common shared project from your own team project you have two<br />

options:<br />

• Branching<br />

• Workspace mapping<br />

Branching<br />

Branching is the preferred method for most shared-source scenarios. It enables you to<br />

pull the shared source into your project and check it into your team project’s source<br />

control. In this scenario, you branch the source from the common shared location into<br />

your team project. This creates a configuration that unifies the source from the shared<br />

location and your project on the server-side.<br />

Shared source changes are picked up as part of a merge process between the branches.<br />

This makes the decision to pick up changes in the shared source more explicit and easier<br />

to test, but it also adds some overhead. Additionally, this process makes the use of <strong>Team</strong><br />

Build much simpler because the mapping is done on the server side; there is no clientside<br />

mapping that needs to be duplicated on the build server.<br />

For example, if you have two team projects named $<strong>Team</strong>Project1 and $Common, and<br />

Common is the shared project source, you create a branch from the shared location to the<br />

project that references it. The TFS folder structure should resemble the one shown in<br />

Figure 6.2.

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

Saved successfully!

Ooh no, something went wrong!