Problem deleting workspace and VS freezing
One of our VS 2005 developers got wrapped around the axle so that VS would freeze on him trying to open any C# solution. He has already done an install/repair of VS, and attempted do delete his workspace. He swears everything was checked in for his workspace, but the deleted workspace keeps re-appearing. Deleting the workspace appears to work, except that the workspace will come back to life, sometimes in the same session, for sure if you close VS and reopen it.
We have already deleted the TFS cache on his machine once. What gives? No one else has the freezing problem either.
[722 byte] By [
jackfox] at [2008-1-8]
Well I haven't heard of this in the past.
One thing to try:
1) Close all intances of VS on the machine.
2) Run a Visual Studio Command Prompt
3) Switch to a directory the user has mapped in the workspace to delete
4) Run tf workspace /delete <workspacename>
5) Run tf workspaces /s:http://<servername>:8080
The output from workspaces should not include the workspace that was just deleted.
This will avoid any potential caching problems and should contact the server to remove the workspace.
Other issues that may happen:
Have you backed up and restored you server to another machine?
How many TFS Servers does the user connect too?
Here are the steps we took:
1) tf workspaces /s:http://<servername>:8080 (shows rogue workspace)
2) tf workspace /delete <workspacename>
3) tf workspaces /s:http://<servername>:8080 (rogue workspace is gone, no workspaces for user)
4) delete local TFS cache
5) reboot machine
6) fire-up VS, and there is the rogue workspace again!
BTW the workspace has the same name as his machine (could that be significant?)
We assume this corrupt workspace is preventing him from working on VS. In the past when we encountered serious VS problems, the solution was always to delete the workspace and start over.
Ah ha, yes VS requires that you have a workspace when you connect to the server. It will create the "default" workspace if you don't have one when it connects. If you don't want this workspace you can delete is from the command-line and create the one you want. Now VS will use this as the workspace.
