Menu
I have managed to corrupt my local Visual Studio Team Foundation Server workspace mappings. Visual Studio can successfully connect to TFS and I can manage the TFS Server connections. However, I cannot open Source Control Explorer or the Workspaces/Manage Workspaces dialogue. Both windows fail with the following message: "Error Unexpected end of file.". From my local machine I also cannot get any information about my workspaces from the tf.exe command line which fails with the same error message "Unexpected end of file."
I would like to note that TFS/database still has my workspaces mapped correctly since I can successfully retrieve information about them from a different machine.
I would like to repair or remove whatever local file Visual Studio is using to map the workspaces. Does anyone know where this information is stored?
896
From Visual Studio, go to the Team Explorer Connect page (Keyboard: Ctrl + 0, C) and then connect to the project. (If the project you want to open is not listed, choose Select Projects and then connect to the project.) Map the project to a folder on your dev machine. Map the workspace and get your code.
Goto team explorer . right click on your ts project and select remove mapping. The folder mapping doesn't showup for the domain\User. it only gives a error if i trying to map the folder to local folder saying the "folder is already is use for the workspace [worksapceName] for domain\AuthorizedTFSUser".
I've fixed my issue where Visual Studio was unable to open Source Control Explorer and Workspaces/Manage Workspaces dialogue by deleting the cache folder located here at:
%localappdata%\Microsoft\Team Foundation\5.0\Cache
Once this folder was deleted reopening Visual Studio was able to connect to Source Control Explorer and I can once again manage my workspaces from the IDE. (Visual Studio created a new cache folder in the same location after starting)
166
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
