If you are having a problem using Vault, post a message here.
Moderator: SourceGear
-
gkustas
- Posts: 5
- Joined: Mon Feb 23, 2004 12:28 pm
Post
by gkustas » Wed May 26, 2004 11:08 am
I just upgraded Vault to 2.0.3 on both client and server. Running the vault client works fine, but my visual studio integration is gone. It is now back to looking for Visual Sourcesafe. I tried uninstalling and re-installing the vault client (of course checking the box that says "use vault as default source control"). Nothing works! PLease help.
-
gkustas
- Posts: 5
- Joined: Mon Feb 23, 2004 12:28 pm
Post
by gkustas » Wed May 26, 2004 11:24 am
After digging through the registry, I found the key that was not changed properly by the vault installer:
in HKLM\SOFTWARE\SourceCOdeControlProvider, set ProviderRegKey to "SOFTWARE\SourceGear\Vault Client"
-
jclausius
- Posts: 3706
- Joined: Tue Dec 16, 2003 1:17 pm
- Location: SourceGear
-
Contact:
Post
by jclausius » Wed May 26, 2004 11:48 am
Another option: if you take a look at the Vault Options (from within the GUI client), there is a checkbox under the General section to make Vault your default Source Code Control Provider.
Jeff Clausius
SourceGear
-
bcupps
- Posts: 1
- Joined: Tue Apr 27, 2004 3:52 pm
- Location: Birmingham, AL
Post
by bcupps » Wed Jun 02, 2004 8:19 am
jclausius wrote:Another option: if you take a look at the Vault Options (from within the GUI client), there is a checkbox under the General section to make Vault your default Source Code Control Provider.
So if we check this box, we don't have to edit the registry?
-
jclausius
- Posts: 3706
- Joined: Tue Dec 16, 2003 1:17 pm
- Location: SourceGear
-
Contact:
Post
by jclausius » Wed Jun 02, 2004 9:24 am
That is correct.
When this option is enabled, the Vault client will make the necessary changes to the system so Vault is available within Visual Studio.
Jeff Clausius
SourceGear