I had a similar issue:

[Sample TFS] $ "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\tf.exe" workspace -delete "Hudson-Sample TFS-DEXAP206" -noprompt -server:http://dexbm201:9010/tfs ********
[Sample TFS] $ "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\tf.exe" workspace -new "Hudson-Sample TFS-DEXAP206" -noprompt -server:http://dexbm201:9010/tfs ********
[Sample TFS] $ "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\tf.exe" workfold -map $/GallioSample . "-workspace:Hudson-Sample TFS-DEXAP206" -server:http://dexbm201:9010/tfs ********
[Sample TFS] $ "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\tf.exe" get . -recursive -noprompt ********
All files are up to date.

The difference is that I'm migrating from TFS 2005 to TFS 2012. From TFS 2010 there is the new concept of collections. I think basically you need to substitute the -server option with -collection option. If your TFS has been migrated, your project may now be part of the "DefaultCollection". So -server:http://ndevic-ids07v:8080/tfs becomes -collection:http://ndevic-ids07v:8080/tfs/DefaultCollection

Here are the modifications I made to the console output. This one works for me.

"C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\tf.exe" workspace -delete "Hudson-Sample-Col TFS-DEXAP206" -noprompt -collection:http://dexbm201:9010/tfs/Sandbox
"C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\tf.exe" workspace -new "Hudson-Sample-Col TFS-DEXAP206" -noprompt -collection:http://dexbm201:9010/tfs/Sandbox
"C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\tf.exe" workfold -workspace:"Hudson-Sample-Col TFS-DEXAP206" -map $/GallioSample/GallioSample ./GallioSample
"C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\tf.exe" get .\GallioSample -recursive -noprompt

Note my get is more explicit otherwise everthing in the collection (at the same level as your project) is extracted.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to