Visual Studio 11 adds local workspaces to the source control feature set. This is a fantastic addition! Previously, if a developer wanted to work offline, they were blocked by read-only flags due to server side workspaces. Now, one is able to differentiate their workspaces between a local workspace and server workspace. Local workspaces gives the ability for a developer to disconnect from the TFS server, make changes to their code, and have Visual Studio track those changes automatically. They will also be able to save these changes! Whereas, server workspaces work just like workspaces in Visual Studio 2010.
Figure 1: Pending Changes view in Visual Studio 11
There is also a new Pending Changes view in the Team Explorer that gives a ton of information on your pending check in. From this view you are able to shelve pending changes, request a review, find shelvesets, resolve conflicts, etc. No more right-clicking and searching these in a menu! Another great addition is that Visual Studio will automatically detect changes outside of it’s environment (i.e. when editing a file via Notepad) as well as added files, deleted files, etc. In the view, the Excluded Changes section (see Figure 1) will have detected changes. The detected change in Figure 1 is an added text file that was done via Windows Explorer. You can now just click the Detected changes link and quickly promote these files to the Included Changes section.
There are also more nice little quirks that were added to local workspaces that I go through in the following video.
Figure 2: VIDEO – Local Workspaces in Visual Studio 11
Find other related Dev on Demand Videos.
Do you want to move to Visual Studio 11 NOW? It is available for install today! For help moving forward, please contact Rick.Flath@nwcadence.com.