Side-by-side installations
Moderator: SourceGear
-
- Posts: 6
- Joined: Mon Jun 04, 2007 12:33 pm
Side-by-side installations
Is it possible to have side-by-side installations of Vault 3.5.2 and Vault 4.0?
-
- Posts: 6
- Joined: Mon Jun 04, 2007 12:33 pm
Probably, providing you're connecting to two different Vault Servers. Install one client, then rename the client directory and install the next client.
Note that if you are using Visual Studio integration, things could get confusing, since the registry for source control provider will point to the last client installed.
However if you are using MSSCI integration with 3.5.2 and 2005 integration with Vault 4.0, that might work.
Note that if you are using Visual Studio integration, things could get confusing, since the registry for source control provider will point to the last client installed.
However if you are using MSSCI integration with 3.5.2 and 2005 integration with Vault 4.0, that might work.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 6
- Joined: Mon Jun 04, 2007 12:33 pm
More details:
There are some known issues with running multiple Vault client versions on a single machine. Both clients share registry entries, so some odd things may happen due to changes in what is actually stored in the registry by different versions, for example:
• Profiles – You will not be able to auto connect using profiles with the both versions of the client.
• IDE Client - If you use the MSSCCI IDE (2003), the installer changes registry settings for SCCServer path in this key HKEY_LOCAL_MACHINE\SOFTWARE\SourceGear\Vault Client. If you just installed Vault 4.x but want to use IDE integration with Vault 3.x you'd need to edit this path to point to the correct Vault Client directory: C:\Program Files\SourceGear\<Vault Client v.2 dir>\VaultIDE.dll.
There are some known issues with running multiple Vault client versions on a single machine. Both clients share registry entries, so some odd things may happen due to changes in what is actually stored in the registry by different versions, for example:
• Profiles – You will not be able to auto connect using profiles with the both versions of the client.
• IDE Client - If you use the MSSCCI IDE (2003), the installer changes registry settings for SCCServer path in this key HKEY_LOCAL_MACHINE\SOFTWARE\SourceGear\Vault Client. If you just installed Vault 4.x but want to use IDE integration with Vault 3.x you'd need to edit this path to point to the correct Vault Client directory: C:\Program Files\SourceGear\<Vault Client v.2 dir>\VaultIDE.dll.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Are there plans to fully support side-by-side client installations? For those of us accessing more than one Vault server, it can be a daunting prospect to coordinate the upgrade of two servers and two (or more) development teams at the same time. I'm still using version 3.1 not because I'm not interested in the new features of 3.5 and 4.0 but because upgrading everyone at the same time is such a big deal.
Thanks,
- David
Thanks,
- David
I can add a feature request to make this easier for users who need to access different Vault servers with different versions.
Upgrading shouldn't be too much of a problem if everyone is using the same server, though -- just run the installers over the current installations on the server and client machines. (Back up the Vault database before upgrading the Vault server).
Upgrading shouldn't be too much of a problem if everyone is using the same server, though -- just run the installers over the current installations on the server and client machines. (Back up the Vault database before upgrading the Vault server).
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager