Dangerous Problem with Branched projects

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
nickbell
Posts: 14
Joined: Fri May 30, 2008 6:20 am

Dangerous Problem with Branched projects

Post by nickbell » Fri May 30, 2008 6:30 am

Hi, I am using Sourcegear Vault 3.1.9 with Visual Studio 2003. I have a project tree with dozens of projects in it which I have branched to a new folder for a new version. For argument sake lets call the original tree Proj_Old and the new tree Proj_New. Each time I open a solution in Proj_New in Visual Studio the Working Folder location for the corresponding solution in Proj_Old gets changed to local folder for Proj_New. This is very dangerous as a Get Latest Version or Check Out will then get the wrong files from Proj_Old and overwrite any changes make on disk to Proj_New.

I have tried using the Change Source Control option in VS to re-bind to the correct location in sourcegear but each time I re-open the project the same thing happens. Can you please explain why this happens and tell me how it can be resolved.

Thanks

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Fri May 30, 2008 7:13 am

This was seen before with Visual Studio: Branching a project stills checks out file from trunk in IDE

When rebinding, you need to make sure you first have it completely unbound. Unbind the project, click OK, save it to disk that way. After that, then go into the change bindings dialog again to perform the bind.

If it still fails after that, let me know.

Post Reply