Vault 4.03 Client install issues

davidvines · Post by **davidvines** » Thu Aug 02, 2007 6:31 am

First issue: the readme info displayed during the 4.03 installation contains 4.02 information.

Second issue occurs when in VS2005, I go to Tools > Options, select the Source Control node, and try to select "SourceGear Vault Visual Studio 2005 Client". Visually what happens is, the combo does not allow me to make the selection. Underneath, it feels like the 2005 Client is failing to load.

Tried uninstalling and reinstalling 4.03, but to no avail.

Using VS2005 SP1

Beth · Post by **Beth** » Thu Aug 02, 2007 7:58 am

Was this a new install or an upgrade?

davidvines · Post by **davidvines** » Thu Aug 02, 2007 8:47 am

An upgrade.

The funny thing is, the install worked initially I think. That is, at one time I I was able to select the 2005 plugin. Then I did something (to do with a project bound to 2003 perhaps ???) that brought about the current state.

And on another system, the 2005 plugin is selectable. That was an upgrade too.

Is there a way (via register settings or file deletions) to make VS 2005 forget it ever knew about Vault? I'd like to try installing totally clean.

Beth · Post by **Beth** » Thu Aug 02, 2007 10:27 am

Did you ever get any errors saying it couldn't load VSIP? When it says something about disable loading that, you have to select 'no'.

If you had a project bound to the 2003 compatible client, then you need to go through the process of switching it to the 2005 client: Re-binding a solution for use with the Vault VS 2005 Client

When you are trying to do this switch to the VS2005 client, do you have a project open?

davidvines · Post by **davidvines** » Thu Aug 02, 2007 12:04 pm

>>>Did you ever get any errors saying it couldn't load VSIP?

The rings a bell. But I'm not certain that was it.

>>>If you had a project bound to the 2003 compatible client, then you need to go through the process of switching it to the 2005 client: Re-binding a solution for use with the Vault VS 2005 Client

Ok.

>>>When you are trying to do this switch to the VS2005 client, do you have a project open?

No.

Beth · Post by **Beth** » Thu Aug 02, 2007 1:43 pm

>>>Did you ever get any errors saying it couldn't load VSIP?

The rings a bell. But I'm not certain that was it.

This part is very important. The VSIP interface I think is on the VS side. Can you do a repair install on VS to see if it puts that interface back in?

davidvines · Post by **davidvines** » Thu Aug 02, 2007 2:13 pm

Funny you should suggest that. I just did that...drum roll...and it worked!

Great minds etc.

davidvines · Post by **davidvines** » Fri Aug 03, 2007 8:32 am

One more thing: instead of reinstalling VS, I think the following command could do the trick:

devenv /resetskippkgs

It's worth a try!

ian_sg · Post by **ian_sg** » Fri Aug 03, 2007 8:53 am

davidvines wrote:devenv /resetskippkgs

I just came here to post that this is the quick way to fix that issue. Thanks for beating me to it.