Vista, VS2003+SP1 & SourceGear Vault 3.5.1 Client

mihutchinson · Post by **mihutchinson** » Mon Feb 26, 2007 9:34 am

I can't get VS2003 to see the vault client in the source control list for Source Control Providers in VS.NET2003.

I have tried al sorts, has anyont here done it?

I open VS2003 and tools>options

I select SCC Provider, but all that is there is VSS, custom and Indipendant options. Can anyone help me?

Mark

Beth · Post by **Beth** » Mon Feb 26, 2007 10:17 am

Have you tried setting Vault as your default SCC provider? That would be in the Vault GUI under Tools - Options - General.

mihutchinson · Post by **mihutchinson** » Mon Feb 26, 2007 11:23 am

Hi Beth, I have set it as default durring the install. VS2003 seem to always show VSS. I thought it may be a Vista issue, hense I want to know if anyone has done it before.

Mark

Beth · Post by **Beth** » Mon Feb 26, 2007 11:50 am

Are you sure VS2003 is even supported on Vista? A report I read said VS2003 wouldn't be supported on Vista. Here's what I had seen: http://www.infoworld.com/article/06/09/ ... ate_1.html and http://blogs.msdn.com/somasegar/archive ... 72250.aspx.

I would still suggest just checking in the GUI to see if the option to make it the default is marked there.

darrenG · Post by **darrenG** » Fri May 25, 2007 9:20 am

I have gotten Vault Client 3.5.1 (4786) to work in Vista with VS2005 Sp1.

Though I am experiencing the same issue in trying to work with VS2003. I understand VS2003 isn't supported for Vista but I haven't found anything entirely broken with it yet.

I set the "Make Vault your default SCC provider" check under options, and also uninstalled and reinstalled the vault client checking to make vault the default source code control provider at install time.

Has anyone gotten VS2003 to recognize vault as an SCC provider? But that I mean have the "Source Control" menu item show up in the Visual Studio 2003 File menu.

Thanks,

Darren

lbauer · Post by **lbauer** » Fri May 25, 2007 9:49 am

I understand VS2003 isn't supported for Vista but I haven't found anything entirely broken with it yet.

Except for source control integration.

Vista is very protective of its registry. When you check the "Make Vault my SCC Provider" box in the Vault client, it edits the registry. It's possible that's not happening on Vista. check to see if you have these registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders

HKEY_LOCAL_MACHINE\SOFTWARE\SourceGear\Vault Client

darrenG · Post by **darrenG** » Fri May 25, 2007 12:17 pm

Ok I got it working!

Both keys existed in the registry

HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders
HKEY_LOCAL_MACHINE\SOFTWARE\SourceGear\Vault Client

By comparing to a XP registry on a coworkers computer I added a string value at:

HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider

Name:ProviderRegKey
Value:SOFTWARE\SourceGear\Vault Client

Seems to be working so far

Thanks,
Darren