Change VS Bindings from Vault Standard to Vault Professional

[Beth]

Changing Visual Studio Bindings from Vault Standard to Vault Professional

When you use Vault integration with Visual Studio, Vault creates connection information to associate your working folders with the repository folders that contain your Visual Studio solutions. These are called "bindings" and are written into solution and project files if you are using the Enhanced Client integration, or into the MSSCCPRJ.SCC file and .vssscc files if you are using Classic Client integration.

Vault Standard and Vault Professional use different binding information. Because of this, when you upgrade from from Vault Standard to Vault Professional, you need to rebind your Visual Studio solutions to use Vault Professional bindings.

Unbinding before you upgrade from Vault Standard to Vault Professional

• The easiest way to make a bindings change between Vault Standard and Vault Professional is to unbind your Visual Studio solutions just before you upgrade to Vault Professional. Click here for details .

Unbinding and rebinding after upgrading from Vault Standard to Vault Professional

• If you have already changed your Vault Standard Server to Vault Professional without unbinding your Visual Studio solutions from Vault Standard, you will get binding errors when you use Visual Studio. To unbind your solutions and rebind to Vault Professional follow these steps: Click here for details.

[Beth]

Unbinding Visual Studio solutions before upgrading from Vault Standard to Vault Professional

The easiest way to make a bindings change between Vault Standard and Vault Professional is to unbind your Visual Studio solutions just before you upgrade to Vault Professional, then rebind after the upgrade to VaultPro client and server. Here are the steps:

Note: If you have already upgraded from Vault to Vault Pro, then CLICK THIS LINK


a) Check out the .sln and project files that are currently bound to Vault Standard.

b) Open your solutions in Visual Studio.

c) Go to File - Vault Source Control - Change Bindings if using the the Vault Enhanced Client, or File - Source Control - Change Source Control if using the Vault Classic Client..

d) Select all the lines in the window that opens and click Unbind.

e) Click OK and then save all the changes.

f) Open a Vault GUI client and check in any changed .sln and project files.


After unbinding your solutions, upgrade clients and server to Vault Professional.


When the upgrade is complete rebind your Visual Studio solutions using these steps:

a) Open a solution in Visual Studio.

b) Go to Tools – Options – Source Control - Plug-in Selection. Select a SourceGear Vault Professional client and click OK.

c) Go to File – Vault Source Control – Change Bindings.

d) Select one line that is not the .sln file and click Bind.

FIG 2.JPG (16.85 KiB) Viewed 15391 times

e) You may get a login prompt. Login to VaultPro and select the repository to bind to.

f) When the binding window opens, if a path to the location in Vault isn’t present, click the browse button (a button with an ellipse) to explore the Vault tree.

FIG 3.JPG (12.59 KiB) Viewed 15391 times

g) Select the folder that holds the project you selected and click OK, and then click Bind.

FIG 4.JPG (22.75 KiB) Viewed 15391 times

h) Check that the status for that line is Valid.

i) Repeat on each line, but bind the .sln file last. When all are Valid, click OK.

FIG 5.JPG (16.64 KiB) Viewed 15391 times

NOTE: In some cases it may be possible to select all lines and click Bind. That is only possible if there is some root folder from which all parts of the solution/project can be reached. This isn’t included in the instructions above. The end result in this case would look like:

FIG 1.JPG (35.77 KiB) Viewed 15391 times

j) You will receive a warning about changing the bindings. Choose the option to “Use these bindings anyway.

FIG 6.JPG (15.13 KiB) Viewed 15391 times

k) You may be prompted to check out the changed files. Click Yes.

FIG 7.JPG (11.97 KiB) Viewed 15391 times

l) Check in the changes to the .sln and project files.

m) All other users who work on that solution/project need to use the same integration client. They now need to set their Source Control to the SourceGear Vault Visual Studio Enhanced Client and perform an Open From Vault or Get Latest to get the solutions with the new bindings. Users whose working folder structure is different than the structure in the repository tree should rebind in the same manner you just employed.

[Beth]

Binding Visual Studio solutions after upgrading from Vault Standard to Vault Professional

If you have already upgraded Vault Standard Server to Vault Professional, you will get binding errors when you use Visual Studio. Follow these steps to unbind and rebind your solutions to Vault Professional:

a) Open the solution in Visual Studio.

b) Before the solution opens, you may receive an error:

FIG 8.JPG (14.1 KiB) Viewed 15365 times

c) Click Yes.

d) The solution will open in Visual Studio with no bindings set.

FIG 9.JPG (10.53 KiB) Viewed 15365 times

e) Go to Tools – Options – Source Control – Plug-in Selection, and set the client it should now use and click OK. In this example, I’m choosing the Vault Enhanced Client.

FIG 10.JPG (30.63 KiB) Viewed 15365 times

f) Go to File – Vault Source Control – Change Bindings.

NOTE: In some cases it may be possible to select all lines and click Bind. That is only possible if there is some root folder from which all parts of the solution/project can be reached. This isn’t included in the instructions below. The end result in this case would look like:

FIG 11.JPG (35.41 KiB) Viewed 15365 times

g) Select one line that is not the .sln file and click Bind.

FIG 12.JPG (16.77 KiB) Viewed 15365 times

h) You may have to first select the repository to bind to and login to Vault.

i) When the binding window opens, if a path to the location in Vault isn’t present, click the browse button (a button with an ellipse) to explore the Vault tree.

FIG 13.JPG (12.54 KiB) Viewed 15365 times

j) Select the folder that holds the project you selected and click OK, and then click Bind.

FIG 14.JPG (22.6 KiB) Viewed 15365 times

k) Check that the status for that line is Valid.

l) Repeat on each line, but bind the .sln file last. When all are Valid, click OK.

FIG 15.JPG (16.5 KiB) Viewed 15365 times

m) You will receive a warning about changing the bindings. Choose the option to “Use these bindings anyway.

FIG 16.JPG (15.09 KiB) Viewed 15365 times

n) You may be prompted to check out the changed files. Click Yes.

FIG 17.JPG (11.81 KiB) Viewed 15365 times

o) Check in the changes to the .sln and project files.

p) All other users who work on that solution/project need to use the same integration client. They now need to set their Source Control to the SourceGear Vault Visual Studio Enhanced Client and perform an Open From Vault or Get Latest to get the solutions with the new bindings. Users whose working folder structure is different than the structure in the repository tree should rebind in the same manner you just employed.