Can Vault 1.1.2 co-exist with Vault 3.5 or 4.0?

BowneUser · Post by **BowneUser** » Tue Sep 11, 2007 1:07 pm

I have to migrate a .NET 1.1 project that is checked into Vault 1.1.2 to whatever new version we purchase of Vault and have it use the .NET 2.0 framework and run under Visual Studio 2005.

I think upgrading from Vault 1.1.2 to either 3.5 or 4.0 would be too difficult and error prone. If there is a way to have Vault 1.1.2 co-exist with Vault 3.5 or 4.0 of Vault that would be the best choice I think. Please let me know how this can be accomplished.

Actually, what is the latest version of Vault? I see that there is a new announcement regarding the release of 3.5 but I thought 4.0 was the latest according to the homepage.

lbauer · Post by **lbauer** » Tue Sep 11, 2007 3:23 pm

You can't have two Vault servers/databases on the same machine. You could install one of the versions on a different machine. However Vault 1.1.2 does not support VS 2005. This support did not come until Vault 3.1.9.

We'd recommend you backup your 1.1.2 database, then uninstall Vault, leaving the database. Then upgrade in increments -- Vault 2.0.6, 3.0.7, 3.1.9, then 3.5.2. I'd stay at 3.5.2 for the time being, until you're familiar with all the changes.

Your database will be upgraded, and you should be able to open your Visual Studio project in VS 2003 (assuming that's what you used before).

Make sure all is ok. Then close the project and open it with VS 2005, which will convert the project to the new format.

Regarding releases: Vault is currently at 4.0.4, but we do have a maintenance release planned soon for Vault 3.5.3, to fix some bugs for users who don't want to upgrade just yet. These bug fixes will be incorporated into Vault 4.0.5, due out in a few weeks.