Source control bindings of projects after branching

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Locked
Ward Bekker
Posts: 11
Joined: Thu Jan 26, 2006 8:24 am
Contact:

Source control bindings of projects after branching

Post by Ward Bekker » Thu Feb 09, 2006 2:59 am

I branched a (older) labeled version of a solution and did an open solution from source control in VS 2005. The solution was opened correctly, but apparantly the bindings still referred to to the original branch, causing the projects to reflect the latest version, instead of the older labeled version.

I can work around it by doing a getlatest on the branched solution from the vault client and then opening the solution in VS2005 in offline mode, unbinding the solution and then manually change the binding to the locations inside the new branch, but that takes a lot of time if you have a lot of projects (20+) in one solution.

Is there a better way to do this? Because I need to switch between different branches quite frequently.

Ward

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Thu Feb 09, 2006 8:47 am

Unfortunately, this is a Visual Studio issue and a known problem. See http://support.sourcegear.com/viewtopic.php?t=1917 for our KB article, which links to MS's article about it.

Locked