Problems branching a VS2003 project

[benwillkommen]

I am working on a web project that uses Vault but has yet to take advantage of branching. I would really like to use this feature, but I am running into trouble.

Initially the repository looks like this:


I want to branch the $/JockeyECommerce directory. I create a new directory in the root called JockeyECommerce-Branches which will contain a branch for each new feature we're developing. I then right click the $/JockeyECommerce directory to open the branch dialog, select the new $/JockeyECommerce-Branches directory and name the new folder after a new feature. he repository now looks like this:


I set the working directory of $/JockeyECommerce-Branches to be C:\WorkingFolder\JOCKEYECOMMERCE-Branches, and do a get latest recursively. After that, I open the .sln file of the project I want to work on, located at C:\WorkingFolder\JOCKEYECOMMERCE-Branches\AjaxAddToBag\ECOMMERCEPORTAL. When I do this, I get the following alerts:





After that, when I view the properties of a file in VS, it says it is located at C:\Inetpub\wwwroot instead of the working directory I selected, C:\WorkingFolder\JOCKEYECOMMERCE-Branches.

How can I open the branched solution?

[Beth]

Have you tried unbinding and then rebinding the project and solution? See this KB article for details: http://support.sourcegear.com/viewtopic.php?t=194.

[benwillkommen]

I am using VS2003 and Vault 4.1.4. Does this fix still work? At the bottom of the article it says, "These steps do not work for VS.NET 2003 and Vault 3.5.1".

[Beth]

But right after that, it says that bug that prevents this from working is in the next update. You should be able to rebind with Vault 4.1.4.

[benwillkommen]

Right, I saw that. The sentence "These steps do not work for VS.NET 2003 and Vault 3.5.1" is a bit ambiguous, and I wasn't sure if it was intended to be logically equivalent to "These steps do not work for VS.NET 2003. These steps do not work for Vault 3.5.1." or "These steps do not work for the combination of VS.NET 2003 and Vault 3.5.1". If the first interpretation is assumed, then the fact that the bug is fixed in the next version would be irrelevant.

Anyway, I followed the instructions and rebound, but it did not seem to do anything except check out all the files in the solution (they are only listed in the pending checkins in VS, they do not show up in the vault client). I then tried to check in the EcommercePortal project so see if it would be checked into the right place. Instead of checking in the files into the ECOMMERCEPORTAL directory, it made a new directory inside ECOMMERCEPORTAL called EcommercePortal and then put the files there. After that, I checked out a css file using the VS integration just to see what would happen, and instead of being in my WorkingFolder, it went into Inetpub.


It seems like a large part of the problem could be how disorganized our projects/solutions are; we have a fairly large legacy code base that has sort of organically grown overtime. I saw on another post that you were able to provide remote assistance to someone with a similar problem, and I think that could be helpful. Could we arrange to set that up?

[Beth]

Sometimes taking a closer look helps. Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?