Sometimes when you're working with the tf.exe and tfpt.exe command-line tools you'll come across this error:
D:\code\ProjectX>tf.exe checkout MyFile.cs Unable to determine the workspace.
D:\code\ProjectX>tf.exe checkout MyFile.cs
Unable to determine the workspace.
This error happens when the command can’t find which local directory maps to which server path.
Obviously, the first thing to check is your workspace mappings. Is the local folder actually mapped? You can do this two ways:
Each of these will show you all the available workspaces and their mappings.
=============================================================================== Workspace: MyWorkspace_ProjectX Owner : user Computer : MYCOMPUTER Comment : Server : tfs-server $/ProjectX: D:\code\ProjectX
===============================================================================
Workspace: MyWorkspace_ProjectX
Owner : user
Computer : MYCOMPUTER
Comment :
Server : tfs-server
$/ProjectX: D:\code\ProjectX
If the workspace mapping exists on the server, then your mappings cache file may need to be refreshed. Try running this command to populate/refresh the cache:
tf workspaces /s:http://tfs-server:8080
This will force your machine to update its local server-to-folder mappings cache file. This file is located at %LOCALAPPDATA%\Microsoft\Team Foundation\2.0\Cache in Vista.
I’ve been looking at my blog stats for the last couple of months to see what people find valuable on
Thank you for your post. Unfortunately, it didn't help me, but I did find the solution:
Whereas Windows file paths are case-insensitive, TFS workspace detection is case-sensitive.
I use a shortcut to open the vs command prompt. The shortcut had start in as "D:\projects...", and that's what I see as the prompt when I click the shortcut. However, the actual file system path is "D:\Projects...". Because of this difference,
TFS was not finding the workspace.
I was facing through the same problem of not recognizing the workspace.
The post about refreshing the cache by "tf workspaces /s:http://tfs-server:8080" was very useful to me
Thanks a lot :)
Since this is the first place google brought me to...I should mention I was getting the exact same error and it was really frustrating that nothing I found on the web was helping until I figured out that my path was executing the 2008 tf.exe when it needed to be the 2010 tf.exe version.
@Marielle: thanks so much for commenting, that was my issue too. (running 2008 tf.exe when I should be running 2010)
Thank you, I was running TF.exe from VS 2005, I needed it to be VS 2010!