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.
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.
g) Select the folder that holds the project you selected and click OK, and then click Bind.
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.
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:
j) You will receive a warning about changing the bindings. Choose the option to “Use these bindings anyway.
k) You may be prompted to check out the changed files. Click Yes.
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.