How to handle two versions of vault on 1 computer?

Henrikop · Post by **Henrikop** » Fri Jul 04, 2008 9:09 am

If have two customers working with Vault server and client but on different version (4.x).

I have a laptop and I'm working on both projects but when I connect to the client with the newest version I get:
The server uses a protocol that is not supported by this client.

What do I have to do the work for both customers on 1 laptop?

lbauer · Post by **lbauer** » Fri Jul 04, 2008 2:04 pm

What exact versions of the Vault Server are you connecting to?

Henrikop · Post by **Henrikop** » Fri Jul 04, 2008 2:26 pm

4.04 I have
4.1.2 is what my other customer has.

Henrikop · Post by **Henrikop** » Tue Jul 08, 2008 2:08 am

I'm still searching for a solution. What would be the cleanest way to archive this? And are the Add-ins of VS changed between those versions?

Is there a link to read? I have found several posts, but these where older posts and about different versions.

lbauer · Post by **lbauer** » Mon Jul 14, 2008 3:14 pm

In your situation, I would suggest upgrading your installation to Vault 4.1.2. We've made a number of bug fixes, plus it's free upgrade since you already have Vault 4.x licenses.

But if you can't upgrade, read on:

It is possible to use two different Vault GUI Client versions on the same client machine.

First, install the Vault client VersionA, if it's not already on the machine. Then copy the files in the Vault client VersionA directory and put them into a folder somewhere else on your drive. Then install Vault client VersionB. You should be able to use each client from its own directory.

The tricky part is IDE integration. If you are using the new Visual Studio Enhanced client, integration with Vault 4.x you can only use Enhanced integration with the last client installed. The installer adds several registry entries for Enhanced client integration, so it's not possible to switch betweens Vault client versions for Enhanced integration.

Some options:

You could use Classic integration for one of the Vault Client versions and Enhanced for the other.

Or if you are using Classic Client integration with both clients, you would need to make some registry changes for Source Control Provider when you switch between clients.

The path to the integration DLL is in the registry under this key:

HKEY_LOCAL_MACHINE\SOFTWARE\SourceGear\Vault Client

You will need to change this path to the proper client directory, depending on which client you are using for your IDE integration.

Here's more information on the new options for IDE integration:

http://support.sourcegear.com/viewtopic.php?t=8535

Henrikop · Post by **Henrikop** » Tue Jul 15, 2008 1:42 am

Wow,

I still got an answer you'd given me years ago. So what this means is that the problem is not acknowlegded by SourceGear!

This is really bad practice.

As a developer I have no power over my customer developer teams, I cannot force a my clients to be "in sync" with Vault version.

A solution would be to work with virtual computers but that will mean more licenses of Visual Studio, more work with all updates and a penalty on the performance of my computer.

This is really dissappointing. I like Vault and using it a lot, when I got new clients I always ask them to use Vault because it works over the internet without hassle.

If there's one oppertunity for Vault, solving this would be it...

lbauer · Post by **lbauer** » Tue Jul 15, 2008 8:21 am

I'll log a feature request for a way to install two different versions of the Vault Client on the same machine. The main sticking point is the ability to use the Enhanced client with both versions.