Opening Projects Nightmare

[davecourt]

Hi

I have a number of very frustrated colleagues in my office who are having numerous problems with Vault.

The biggest problem however is for a colleague to open a project in Visual Studio from Vault. It has got to screaming point to try and do this and I was really hoping someone might be able to offer some advice/codes of practice for this? Just to add, the colleague is trying to open the solution created by another colleague.

Our projects are made up of a single solution file and multiple projects within the solution. I would expect that if I tried to open a solution file from Source Control ie. Vault, it should copy all the files to the working directory location and then open all the projects from their working directory location - but it doesn't It tends to give an operation not working style error.

Could someone please suggest how I should resolve this issue as I am the one who suggested and implemented Vault and obviously am now the one who is getting the brunt of all the frustrations!

Thanks in advance

Dave

[dan]

Our projects are made up of a single solution file and multiple projects within the solution. I would expect that if I tried to open a solution file from Source Control ie. Vault, it should copy all the files to the working directory location and then open all the projects from their working directory location - but it doesn't It tends to give an operation not working style error.

It should do what you expect, although Visual Studio will determine the working folder locations, and they will be underneath the solution file root folder.

I'll need more details on what exactly is happening - what steps are you taking, and what messages are appearing when?

Also, make sure you look at the output window, and you might also want to turn on client side logging, described at http://support.sourcegear.com/viewtopic.php?t=2898

[davecourt]

Thanks for the reply Dan.

Via Source Vault client, we want to be able to cancel the working folder within a sub folder and set it to inherit from the root directory as you can in SourceSafe.

How are we able to do this?

Thanks

[dan]

In the Set Working Folder dialog, check the "Force all subfolders to use inherited working folder"

[davecourt]

Dan, this tick box doesn't seem to be available to us?

We only have a browse box - we are using 2.0.4?

Thanks

[dan]

That feature was added in the 3.0 release, so you'll need to upgrade to get it. But, I think you can simply delete the working folder entry from the textbox, and it will unset it. Otherwise, you can try things in this thread:

http://support.sourcegear.com/viewtopic.php?t=539#1662

[davecourt]

Thanks again for the response Dan.

How do we upgrade to version 3 to eradicate some of the problems we are experiencing. I know version 3 came out not long after we purchased Vault?

[dan]

If you bought gold support, it is a free upgrade, otherwise, you can buy gold support now and then upgrade (check our website for details). It is an easy upgrade - just download it and install it on top of the existing installation, and import the new licenses, and it shoud be ready.

[davecourt]

Thanks

Is there any information available to show what improvements have been made to the latest version of Vault?

Thanks

[dan]

See the downloads page at http://www.sourcegear.com/vault/releases/3.0.html

[davecourt]

Final question Dan

How many Gold support licenses do we need to purchase in order to upgrade our single server?

Thanks

[dan]

You need one gold support license per named user to upgrade.