Skip to main content

TFS: TF.exe Workspace Maps $/ by Default

Team Foundation Server's (TFS) command-line interface tf.exe workspace option maps a working folder to the server root $/ by default. That I can find, there's no way to turn this off. To combat this behavior, you'll want to unmap the default after adding in your desired folder mapping(s).

>tf workspace /new /noprompt /s:http://TFSRTM08:8080 MyWorkspace

>tf workfold $/SampleProject c:\src\SampleProject /workspace:MyWorkspace /s:http://TFSRTM08:8080

>tf workfold /unmap $/

Comments

Anonymous said…
Thanks! Very helpful!!!
David Atkinson said…
Your post just saved me a lot of wasted time when setting up a CI demo for SQL Server databases. I have been finding the msdn documentation for tf.exe particularly painful to use.

Many thanks!

David Atkinson
Red Gate
bourgon said…
Freaking useful, not just because of the mapping issue, but because I couldn't find anywhere the exact syntax to create a workspace programmatically. Thanks!
Jeff Hutton said…
Thank you. This is the only site on the web having the /noprompt part of the command. The MSDN info has that switch buried in the list, but I missed it. It would be helpful if they had an example of its use.

Regards,

Jeff Hutton
Unknown said…
alternatively, change your working directory before creating the workspace (will then map to that directory instead, by default)

Popular posts from this blog

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)] I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent! I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around. Thanks in advance! Update 7/19/2008: Version Control and Microsoft

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario... I'm worki

Installing the .Net Framework 3.0 SP1 on Windows 2003 Server

I'm building an [automated] build server requiring the .Net 2.0 and 3.0 runtime. Unfortunately, at my client, they leverage a proxy server. The standard .Net 3.0 SP1 framework redist is really just a bootstrapper. Logged in as a local admin on the box, I didn't have the opportunity to authenticate the installation EXE with my domain credentials. So, the install kept timing out. Finally, I found this helpful post from Aaron Ruckman on how to download the very elusive, full framework package. It's here , BTW (x86). I finally get the full installation EXE downloaded to a fileshare, re-run the install and wham--" XPSEPSC: XPS must be installed..." Excuse you? This isn't an XPS ...it's a VM. I found a few MSDN posts here and here outlining the problem. I'm still not clear on what XPSEPSC does (Google yielded little) but you can download it here (x86) . After installing XPSEPSC, the framework installed without issue. Update : Somewhat related, there i