TFS Folders - Getting them to work like Subversion "Trunk/Tags/Branches"

Posted by Sam Schutte on Stack Overflow See other posts from Stack Overflow or by Sam Schutte
Published on 2009-08-14T15:45:50Z Indexed on 2010/04/01 4:03 UTC
Read the original article Hit count: 296

I recently started using Team Foundation Server, and am having some trouble getting it to work the way I want it to.

I've used Subversion for a couple years now, and love the way it works. I always set up three folders under each project, Trunk, Tags, and Branches.

When I'm working on a project, all my code lives under a folder called "C:\dev\projectname". This "projectname" folder can be made to point to either trunk, or any of the branches or tags using Subversion (with the switch command).

Now that I'm using TFS (my client's system), I'd like things to work the same way. I created a "Trunk" folder with my project in it, and mapped "Project/Trunk/Website" to "c:\dev\Website".

Now, I want to make a release under the "tags" folder (located in "Project/Tags/Version 1.0/Website", and TFS is giving me the following error when I execute the branch command:

"No appropriate mapping exists for $Project/tags/Version 1.0/Website"

From what I can find on the internet, TFS expects you to have a mapping to your hard drive at the root of the project (the "Project" folder in my case), and then have all the source code that lives in trunk, tags and branches all pulled down to your hard drive. This sucks because it requires way too much stuff on your hard drive, and even worse, when you are working in a solution in Visual Studio, you won't be able to pull down "Version 2.0" and have all your project references to other projects work, because they'll all be pointing to "trunk" folders under the main folder, not just the main folder itself.

What I want to do is have the root "Project/Website" folder on my hard drive, and be able to have it point to (mapped to) either tags, branches, or trunk, depending on what i'm doing, without having to screw around with fixing Visual Studio project references.

Ideas?

© Stack Overflow or respective owner

Related posts about tfs

Related posts about visual-studio-team-system