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.

Figure 10.1 Large Project Scenario<br />

Figure 10.1 highlights a number of key points about the way in which a large team<br />

project operates:<br />

• Each sub-team maintains its own build server and output builds to a drop point.<br />

• Application teams pick up builds from the component teams, reuse them as part of<br />

their solutions, and include them in their builds.<br />

• Component and integration testing occurs on each build. Bugs are filed in the<br />

appropriate bug database.<br />

Source Control Considerations<br />

If you work on a very large solution requiring many dozens of projects, you may<br />

encounter <strong>Visual</strong> <strong>Studio</strong> solution (.sln) scalability limits. For this reason, you should<br />

organize your source control structure by sub-systems or sub-applications and use<br />

multiple solution files. Divide your application into multiple solutions, but do not create a<br />

master solution for the entire application. Figure 10.2 shows the multiple solutions<br />

approach commonly used by large teams.

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

Saved successfully!

Ooh no, something went wrong!