Branching Web Projects

A collection of information about Vault, including solutions to common problems.

Moderator: SourceGear


Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
PostPosted: Mon Feb 16, 2004 2:39 pm
If a web project is branched in the Vault GUI client but will be accessed via the IDE, the branched project must be unbound and rebound to source control. This is because the original path is hard coded into the "SccProjectName1" line of the solution file.

If this is not done, changes apparently made to the branched version of the project will be checked in to the trunk version. This behavior is controlled either by the Microsoft  integration API or by Visual Studio .NET itself and cannot be changed by the Vault IDE. 

For example, if the following web project is branched in the Vault client:

Code: Select all
$/
  Folder/
    WebApplication1/
      WebApplication/

to:
Code: Select all
$/
  Folder-Branch/
    WebApplication1/
      WebApplication/


The first user to open the "Folder-Branch" version from source control would have to unbind and rebind as follows:

  • Go to File > Source Control > Change Source Control
  • Select Solution: WebApplication1.sln and click Unbind
  • Select WebApplication1 and click Unbind

Note: Be sure to close the Change Source Control dialog box and then reopen it.

  • Select Solution: WebApplication1.sln and click Bind
  • Browse in the tree to $/Folder-Branch/WebApplication1, set a working folder and click OK
Note: Be sure the path shown in the Choose Folder dialog box is correct

  • Select WebApplication1 and click Bind
  • Browse in the tree to $/Folder-Branch/WebApplication1/WebApplication, set a working folder and click OK
Note: Be sure the path shown in the Choose Folder dialog box is correct

  • Click OK to close the Change Source Control dialog box
  • In the Solution Explorer Window, right click on the WebApplication1 solution and select Save WebApplication1.sln
  • Now, Check In the WebApplication1.sln file

Note: This limitation only affects web projects.

Update: These steps do not work for VS.NET 2003 and Vault 3.5.1. There is a bug which causes a problem binding the branch. This will be fixed in Vault 3.5.2

These steps DO work for VS 2005 and later.

Return to Knowledge Base (Vault)

Who is online

Users browsing this forum: No registered users and 2 guests

cron