Changing between classic and VS enhanced plugins

If you are having a problem using Vault, post a message here.
Post Reply
thale013
Posts: 8
Joined: Mon May 14, 2012 8:02 am

Changing between classic and VS enhanced plugins

Post by thale013 » Tue May 15, 2012 9:09 am

I'm having issues integrating with VS 2010 and wanted to try both plugins to see how they would behave. The problem is that I am able to change the default plugin VS 2010 uses to the Classic Client, but when I open the solution I'm trying to work with, I see that VS 2010 has changed default plugin back to the Enhanced Client. If I then go back and change the default plugin back to the Classic Client, VS 2010 warns me that active solution is controlled by a different plugin and I must close it. Any ideas?

I'm running Vault Server and Client version 5.1.2.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Changing between classic and VS enhanced plugins

Post by lbauer » Tue May 15, 2012 10:05 am

Visual Studio creates bindings between the Solution/Project and source control. This binding information is written into Solution and project files (Enhanced Client) or into separate source control files (Classic Client).

If you want to switch between Enhanced and Classic integration, you have the remove the bindings before switching to the other style of integration.

To do this:

First, open your solution. If you are using the Vault Enhanced Client integration, use the menu item "Change Vault Bindings" in Visual Studio under File->Source Control. This will give you an unbind dialog where you can remove the bindings. After you unbind, "save all" to save your unbound solution and project files.

Now that the project is unbound, change the plugin selection to Classic Client.

To rebind to Classic Client integration, look under File->Source Control->Change Source Control in Visual Studio to get the bindings dialog. Click Bind in the Change Source Control dialog. You'll be prompted to log in again. Connect to the Vault server, locate the project in the repository tree, and then click bind. "Save all" again, and be sure to check in your changes.

For more details about Visual Studio/Vault bindings, see this KB article:

http://support.sourcegear.com/viewtopic ... 375#p68375
Linda Bauer
SourceGear
Technical Support Manager

Post Reply