Pesky 'ghost' workspace mappings
Hey guys,
I ran into a situation that I wanted to share. Somehow, I got Team Foundation Server - Team Explorer specifically - into a state where it believed that my desktop folder was mapped to a workspace. I had removed this workspace a long while ago.
Because of this, I could not use my desktop for any workspace mapping.
Even though Team Explorer showed that I have no workspaces, I still could not map my desktop folder.
If this ever happens to you, a good place to check is your cache; the example I show below has some system specific values, but I think you get the idea:
C:\documents and settings\administrator\local settings\application data\microsoft\team foundation\1.0\cache
Some of you will know that this is the location of the work item meta-data cache. It also has the versioncontrol.config file. This is where workspace mappings are stored. If you have a ghost workspace, this is most likely the culprit.
Thanks,
Eric.
posted by ericlee at
8:44 PM
2 Comments:
The cache file stores the workspace mappings per server, and each server is identified by its GUID. When the version control support in VS first connects to a server, it refreshes the cache.
If you had a server set up and then destroyed it and installed a new server, the new server and old server would have different GUIDs. The client won't know that you've replaced the old server with a new server. As a result, the client's cache file has the workspace mappings for the original server still stored using the original server's GUID. Those get stuck there forever until you either do what you did, or you use the "tf workspace /remove:* /s:*" command to clean out the cache.
Once the reference to the old server is removed from the cache, you're good to go. My guess is that you hit this in course of evaluating different releases or whatever.
July 10, 2007 1:49 PM
interesting blog. my blogroll has been updated. http://yasir03.online.fr do come along with some comments when u have time
August 12, 2007 4:07 AM
Post a Comment
Links to this post:
Create a Link
<< Home