It is probably better placed there, as with the TFS powertools my context menu has at least 20 items in it.

Hi Derek,

If you point your VS 2012 RC instance at a TFS 2012 server you'll find TFS workspaces by default are now local. That is, the files you have are tracked locally on your machine, not on the server, avoiding the Force Get issue.

Regards,

Jason

For some of these annoying steps I've come to love setting up a quick function or alias in powershell.

In the $PROFILE I'll put something like

(say my project is called SCOOBY)

function getSCOOBY(){

  tf get /recursive "C:\Code\SCOOBY\*" $args

}

NOTE the $args at the end. This allows me to execute

getSCOOBY /force /overwrite

or any other options needed...

Derek - to be more specific to what others have said - with TFS 2010 ("It gets better" with 2012) - "Big Brother is watching".

TFS expects that you don't do what you did - nuke the directory tree "without telling it".

"The TFS 2010 Way" would have been, after you nuked your repro -  to go to Team Explorer -> Workspace Dropdown and then click "Remove".  

Then you could add the Workspace  back and "Get Latest" works the way you expect.

Yes it sucks - but that's why the fixed it in TFS 2012...  

My God  nasuya ko sa imong scedhule..ako tawn full ko 7:30-12:30 hahays.. dats life! ehehhe Congratulations in advance Bry!.-= bugITs-technology news and updates's last blog .. =-.