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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

For more information about project groupings and solution structure, see “Chapter 03,<br />

Structuring Projects and Solutions in Source Control.”<br />

For more information about branching scenarios and related folder structures, see<br />

“Chapter 5, Defining Your Branching and Merging Strategy.”<br />

Workspaces Explained<br />

A TFS workspace is a client-side copy of the files and folders in TFS source control. A<br />

workspace maps source control folders to local file system directories. When you make<br />

changes to files <strong>with</strong>in the workspace on your local computer, the local changes, referred<br />

to as pending changes, are isolated in your workspace until you check them into the<br />

server as an atomic unit. The collective set of changes, checked in as a batch is referred to<br />

as a changeset.<br />

A single workspace can contain references to multiple team projects. You can also use<br />

multiple workspaces to isolate files or versions for your use only. Workspaces are per<br />

computer, per user account. Therefore, you can have different workspace definitions for<br />

each computer you use. Also, as a single user, you can have multiple workspaces on a<br />

single computer.<br />

Note: You can only map each physical location on the local file system by using a single<br />

workspace. However, you can map each server directory to entirely different local<br />

directories by using different workspaces.<br />

Creating a New Workspace Mapping<br />

Because mappings are recursive, when you create a new workspace mapping and you<br />

perform a Get Latest Version operation at the root of that workspace, the entire local<br />

folder structure is created automatically. The newly created local folder structure matches<br />

the server structure.<br />

Keep the following recommendations in mind when you create new workspace<br />

mappings:<br />

• The project owner must ensure that the correct folder structure is used locally prior to<br />

adding the solution to source control for the first time.<br />

• When establishing a workspace mapping for a team project for the first time and<br />

performing a Get Latest operation, be sure to map the root team project folder into an<br />

appropriate local folder such as C:\DevProjects\<strong>Team</strong>Project1.<br />

Where Are Workspace Mappings Stored?<br />

Workspace information is maintained on both the client and the server. On the client,<br />

workspace information is held in VersionControl.config which is located in the following<br />

folder:<br />

\Documents and Settings\[user]\Local Settings\Application Data\Microsoft\<strong>Team</strong><br />

<strong>Foundation</strong>\1.0\Cache.

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

Saved successfully!

Ooh no, something went wrong!