Re-binding for use with the Visual Studio Enhanced Client

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

Moderator: SourceGear

Post Reply
Posts: 16
Joined: Tue Jul 25, 2006 10:34 am

Re-binding for use with the Visual Studio Enhanced Client

Post by egli » Mon Jun 04, 2007 3:15 pm

For users who have projects that were bound to Vault using the SourceGear Vault Classic Client and now wish to use the SourceGear Vault Visual Studio Enhanced Client, the solution will need to be un-bound using the Classic Client and then re-bound using the Visual Studio Enhanced Client (note, these steps apply to Vault 4.1.0 and later):
**Edit: We've released an automated tool to convert solutions and projects. See

Open the solution in Visual Studio.

Ensure that all project files and the solution file are NOT exclusively checked out by anyone (including yourself).

Open the "Change Source Control" dialog (File->Source Control->Change Source Control...).

Select all bound projects and click the "Unbind" button at the top of the dialog.

When it asks to confirm, click "Unbind".

Click OK to close the "Change Source Control" dialog.

Do a Save All in Visual Studio (File->Save All) to save the solution and project files. (If prompted to overwrite files that are readonly, overwrite the solution file and all project files.)

In Tools->Options, set your "Current source control plug-in" to "SourceGear Vault Visual Studio Enhanced Client".

Open the "Change Vault Bindings" dialog (File->Vault Source Control->Change Vault Bindings).

Select all projects that were formerly bound, and click "Bind...".

At this point, you will be prompted to log into the server and select the repository where the projects exist. Enter your username and password to log in.

In next dialog that comes up (titled "Bind"), click the "..." button to browse to the projects' Deepest Common Ancestor in the repository. Select the folder and press OK on the "Select a repository folder" dialog. Then press Bind on the "Bind" dialog.

You are then returned to the "Change Vault Bindings" dialog. Make sure that all projects that were selected have been marked "valid" in the status column. If any projects are invalid, you will need to unbind them or re-bind them individually.

Once all bound projects are valid, press OK on the "Change Vault Bindings" dialog. This will add changes to the project files to your Pending Change Set.

Perform a Check In to commit these changes to Vault. This can be done by right-clicking on the solution and choosing "Checkin" from the context menu.

After the checkin, you may be prompted to reload the solution and relogin to Vault.
This completes the process of updating the solution to be bound for the SourceGear Vault Visual Studio Enhanced Client. Note that after this point, users will no longer be able to open the solution using the Classic Client. All users must use the Visual Studio Enhanced Client.

Since all other users who have copies of the solution will still have old versions (with the old Classic Client bindings) on their local machines, they will need to do a Get Latest to retrieve the new version. This should be done from the standalone Vault Client as follows:
Open the standalone Vault Client application from the Start menu or Vault shortcut on the Desktop.

Log in and connect to the repository that contains the solution.

Right-click on a folder that contains the solution and all of its projects, and do "Get Latest Version...". Make sure the Recursive option is used.

This will update your local copies of the solution & project files to the versions that are bound for the SourceGear Vault Visual Studio Enhanced Client.

Close the standalone Vault Client.

Then open the solution by double-clicking on it in Windows Explorer, or by opening Visual Studio and selecting it from the list of recent projects in the file menu.

You will be prompted to log into the repository. Enter your username and password at the prompt.
You are now Online using the SourceGear Vault Visual Studio Enhanced Client.

Post Reply