Tuesday, August 08, 2006
Changing the Local Path in Team Foundation Server Source Control
Here is something that drove me crazy until I finally figured it out: We are now using Team Foundation Server for source control instead of various systems we used before (such as VSS). I joined a project, and I was not quite sure what local path to use. Just like with Source Safe, I am never quite sure whether I need to add the actual name of the project folder, or whether it will add that automatically. So long story short: I picked the wrong path.
The trouble now was: How do I change the local path? Once the local path is picked, there is no obvious way to change it again, because all the UI options one uses the first time around are now disabled.
The answer is "workspaces". Visual Studio has a "Workspaces..." menu item under the Source Control menu item in the File menu. This shows the "Manage Workspaces" dialog, which allows each user to manage all their worspaces. A workspace could be a configuration for each machine a user uses (for instance). You can then go and edit individual workspaces, which provides you a list of all local names (local paths) for each project you have ever joined, and this is where you can change the path.
So there: Isn't this intuitive?
Posted @ 5:04 PM by Egger, Markus (markus@code-magazine.com) -
Comments (33)