Mapping a local folder to more than one source control folders

Hi Everybody,

I'm a little bit confused about a restriction in TeamSystem Version Control

I can't map a local folder to more than one source control folders. Example:

I use a workspace 'CurrentVersion' with a Source Control folder $/MyProject mapped to a local folder d:\MyProject.

Now assume there is an old version like $/MyOldProject in the Source Control. To work with this old version I create a workspace 'OldVersion' and try to map my local folder d:\MyProject with the Source Control folder $/MyOldProject. TeamSystem issues the error: 'The path d:\MyProject is already mapped in workspace CurrentVersion.

Why is it not possible to use the same local directory in different workspaces ?

Until now this was the process in our company to handle different versions. We were working on a fix local folder mapped to different SourceControl folders (in Visual SourceSafe this doesn't matter).

Is there a way to handle this, or is there another recommended approach ?

Thanx in advance,

voko

[1072 byte] By [voko] at [2008-2-15]
# 1
Why is it not possible to use the same local directory in different workspaces ?

It would lead to a lot of unnecessary ambiguity.

I'd recommend using branches to service older releases. There are lots of posts about branch/merge guidelines in this forum and on Buck's blog.

Also, chances are you only need 1 workspace -- there's no reason you can't map both branches (to different local folders) at the same time.

RichardBergMSFT at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - Version Control...

Visual Studio Team System

Site Classified