# IT:AD:TFS:Concepts #



<callout type="Navigation" class="small">

* [[../|(UP)]]
{{indexmenu>.#2|nsort tsort}}




---

## Visual Studio Team Explorer ##

* Get to it using [In VS]/[Views]/[Team Explorer]
* Use it to Add/Remove Users as Team Members 
* Use it for WorkItems

## Visual Studio Source Control Explorer ##


</callout>


## Workspaces ##

* A Workspace is -- in essence -- just a set of nested folders, mapped to areas in TFS, containing local copies of files of files and folders in TFS.
* When you edit files, you're making changes to the local files, that need to be at some point checked in -- ie, pushed back the TFS Server.
* A primary benefit for workspaces is isolation. It provides a sandbox to make changes without worrying about affecting other users - at least till the changes are checked in.
* Workspaces can be created as:
    * Private (the Default), 
    * Public (Limited)
    * Public (multiple people can change and check in code.
        * Very useful when sharing a workstation.
* There is no hard rule as to whether to keep:
    * One Workspace per project
    * One Workspace with all projects in it.

## Resources ##

* [Excellent Intro](http://bit.ly/tTgGnA)
* [Indepth Work Item](http://bit.ly/sRAWjW)
* [http://visualstudiomagazine.com/articles/2011/07/26/wctfs_tfs-version-control.aspx](http://visualstudiomagazine.com/articles/2011/07/26/wctfs_tfs-version-control.aspx)
* [http://blogs.msdn.com/b/phkelley/archive/2010/02/04/improvements-to-workspaces-in-tfs-2010.aspx](http://blogs.msdn.com/b/phkelley/archive/2010/02/04/improvements-to-workspaces-in-tfs-2010.aspx)

## Mapping ##

* Read: [http://blogs.msdn.com/b/phkelley/archive/2010/02/04/improvements-to-workspaces-in-tfs-2010.aspx](http://blogs.msdn.com/b/phkelley/archive/2010/02/04/improvements-to-workspaces-in-tfs-2010.aspx)