After restoring the TFS collection on the server yesterday, I was ready to map to the original disk address, but I didn't know why I was mapped by user wws:3 (WWS is the first letter of my name, but: where does 3 come from?). )。
Search data on the Internet, but only to find that said delete C:\Documents and Settings\ current user \local Settings\Application Data\Microsoft\Team Foundation\1.0\ The Versioncontrol.config file in the cache folder, the result is tried, a little response is not, or the hint has been mapped.
Without a clue, look at the previously written TFS forced check-in step, and the result is an inspiration when you see this command
TF Undo/workspace:pc201502261425;wws:3 ...
This command is the file I checked out before I used to force the check-in server to crash. So since I can force check in with a command, why can't I use the command to delete the Wws:3 user's workspace on my computer?
So immediately Baidu TFS Delete the workspace command, get the following code:
TF Workspace/delete/collection:http://yt-net:8080/tfs/et-tfs Pc201502261425;wws:3
Then follow the prompts to enter Yes to execute the command to delete the workspace. When I finished I went back to VS, mapped the original disk path, the mapping was successful.
Recall the entire process, because the server re-WWS the system, so that in order to not conflict with the current user, TFS may automatically add ": Number" to the original user.
Because the colleague mapping, the same situation, but the number is not the same as me, but anyway, as long as the command to delete the TFS Auto-configured users on the local computer mapping workspace, you can map the original path.
Of course, some people will say, you re-map a path is not it? Yes, remapping a path is not a problem, but for me with obsessive-compulsive disorder!
TFS Command TF Delete delete workspace