Branching issue / Visual Studio 2005.

[RyanS]

We have a strange issue while branching.

Here is our current setup in Vault:

v0101/Application/Mainline
/Configuration/
/Framework/
/Projects/
/Solutions/

That is for the main project.

Then for branching we have

v0101/Application/WorkInProgress/
/NameOfFixOrProject/Configuration/
/NameOfFixOrProject/Framework/
/NameOfFixOrProject/Projects/
/NameOfFixOrProject/Solutions/

We are using Visual Studio 2005 and SourceGear 3.5.1 (4786).

When we open a solution from the branch, the solution opens fine however when a file is checked out, it is checked out from the original location (Mainline) and not from the branch.

Opening up the "Change Source Control" it shows that the server bindings are not getting updated in the solution file to point to the new location (WorkInProgress/NameOfFixOrProject).

Any suggestions?

Thanks.

[lbauer]

When you branch a project in Vault 3.5.x, the bindings are not automatically changed. You do need use "Change Source Control" to correct the bindings. You should also be able to open the branch using File->Source Control->Open from Source Control to set the proper bindings.

The new VS 2005 integration client in Vault 4.0.4 properly updates the bindings in branches.

[RyanS]

We do open the solution from File-->Source Control-->Open from Source Control.

Are you saying that even though we open it this way the bindings will still be incorrect and must be manually fixed?

[lbauer]

Are any of these web projects?

[RyanS]

The main project is a web project. The rest are class libraries.

[lbauer]

With web projects, the bindings will still be incorrect, even if you open from source control.

Here's a KB article that discusses the issue:

http://support.sourcegear.com/viewtopic.php?t=194

Note: for these steps to work, I suggest you upgrade to 3.5.3. There was a bug in Vault 3.5.1 that caused even these steps to not properly update the bindings.

[kadorken]

We branched our project using 3.5.2 (5087) from Head to x.x
I then opened the x.x from source control using VS 2005. It appeared to work; however, I later discovered that my 'working' folders in Vault were constantly being reset incorrectly in the Head tree to the x.x tree.
After reviewing the source bindings in Change Source control, I observed NONE of the bindings had been changed from 'Head' to x.x.

I manually redid them all using the procedure you outlined for web services to correct the problem.

Will upgrade to 4.0.x once this version is released....

[lbauer]

Vault 4.0.5, currently in Beta, handles this scenario much better, with the VS 2005-style plugin.
http://support.sourcegear.com/viewtopic.php?t=8756

Info on the new plugin:
http://support.sourcegear.com/viewtopic.php?t=8535
To rebind your projects:
http://support.sourcegear.com/viewtopic.php?t=8214

[kjedrusiak]

We are using VS2005 with Vault 4.0.4 under the VS2003 integration client.

Let's say the project is called CR.

Using the Vault UI I created a branch called CR 2.16 when we put out that version.

Now we have a third programmer working on some test code, so we don't want to polute CR 2.16.

So I created a branch of that called CR 2.16 - P.

Using the Vault UI on the programmers machine we set the working folder to a specific new folder which was created.

Then did a Get All. After the Get All we opened the solution in VS2005, but the bindings are still pointing to the trunk.

Did we mess up royally somewhere?

[Beth]

Can you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread so we can delve a little further into this issue?