Team Development with Visual Studio Team Foundation Server

Additional Resources
• For more information about creating a workspace, see “How to: Create a Workspace”
at http://msdn2.microsoft.com/en-us/library/ms181384(VS.80).aspx
• For more information about editing a workspace, see “How to: Edit a Workspace” at
http://msdn2.microsoft.com/en-us/library/ms245466(VS.80).aspx
Use a Unique Local Folder Path on Shared Computers
Two users of a single computer cannot share the same workspace mapping. For example,
you and a colleague cannot map the same team project ($/MyTeamProject) to the same
folder on the local computer. Instead, create mappings beneath My Documents (although
this leads to long location paths) or establish a team folder naming convention on the
local computer (for example, C:\TeamProjects\User1, C:\TeampProjects\User2 etc).
Additional Resources
• For more information about creating a workspace, see “How to: Create a Workspace”
at http://msdn2.microsoft.com/en-us/library/ms181384(VS.80).aspx
• For more information about editing a workspace, see “How to: Edit a Workspace” at
http://msdn2.microsoft.com/en-us/library/ms245466(VS.80).aspx
Consider Mapping Only Part of the Source Tree
To improve performance and reduce disk-size requirements, only map the files you need
for your development project. In general, you will only need the files and projects
associated with the solution on which you will be working.
Additional Resources
• For more information about creating a workspace, see “How to: Create a Workspace”
at http://msdn2.microsoft.com/en-us/library/ms181384(VS.80).aspx
• For more information about editing a workspace, see “How to: Edit a Workspace” at
http://msdn2.microsoft.com/en-us/library/ms245466(VS.80).aspx
Structure Your Source Tree to Support Branching
Your source tree structure consists of a combination of folder structure, file structure, and
branch structure. Within your main branch, the following folder and file structure has
been proven to work for teams of various sizes:
• Main - container for all assets you need in order to ship the product
o Source - container for everything you need to build
• Code - container for source code
• Shared Code – container for source code that is shared from other
projects
• Unit Tests - container for unit tests
• Lib - container for binary dependencies
o Docs - container for documentation that will ship with the product
o Installer - container for installer source code and binaries
o Tests - container for test team test cases