all source control options are disabled

thadmiller · Post by **thadmiller** » Fri Nov 02, 2007 12:17 pm

I'm running WinXP x64 & VS.Net 2003 - both patched up to date.

Before this morning, I was using VSS 2005 for SCC. I uninstalled VSS 2005 and installed Vault Client 4.0.5 (15922) and from the Vault Client, I checked the box to "Make Vault your default SCC Provider", but all source control options (under the file menu) are greyed out and disabled.

I checked HKLM\SOFTWARE\SourceCodeControlProvider and I have a ProviderRegKey set to "SOFTWARE\SourceGear\Vault Client" (not added manually).

Any ideas on what the issue may be?

-Thad

Post by **jclausius** » Fri Nov 02, 2007 1:47 pm

Which *edition* of Visual Studio .Net 2003 are you using? Standard, Professional, etc.

thadmiller · Post by **thadmiller** » Fri Nov 02, 2007 1:58 pm

Visual Studio.Net 2003 Enterprise Architect

Post by **jclausius** » Fri Nov 02, 2007 3:44 pm

Is the menu File -> Source Control enabled? For any existing projects, you'll need to unbind them using VSS 2005 from the binding dialog, switch back to Vault as the provider and then re-bind.

For VS .NET 2003 and earlier, this was controlled in the registry entry you mentioned. Another option is to look at a tool named 'SCCSwitcher' as it will help make the registry modifications if you want to use multiple providers within Visual Studio .NET 2003

thadmiller · Post by **thadmiller** » Mon Nov 05, 2007 8:08 am

Yes, the File -> Source Control menu item is enabled, but NONE of the child menu items are enabled.

Also, I cannot unbind existing projects using VSS 2005, because I no longer have VSS 2005 installed (which wouldn't seem to be the issue anyway, because even new projects have all the source control options disabled). And I'm not attempting to use multiple providers within VS.Net 2003, so I'm not certain of the usefulness of SCCSwitcher in my case, but I downloaded and installed it anyway - it didn't do any good (the Installed SCC Providers list only contains SourceGear Vault VS2003 Compatible Client - nothing to switch to or from - and the Make Default button is disabled - assuming because it is already the default).

Post by **jclausius** » Mon Nov 05, 2007 9:30 am

Can you test the Source Control Ops on a NEW solution? Does Vault work for anything new?

If this does work, my guess is the solution/project still have bindings to SourceSafe and is causing a conflict within Visual Studio because the DLL is no longer installed. If that is indeed the case, you'll need to modify the solution / project files by hand removing any SCC sections, so Visual Studio thinks things are not bound. Please make a backup of any files before editing the solution or project files.

thadmiller · Post by **thadmiller** » Mon Nov 05, 2007 9:35 am

No, vault does not work on new projects either.

Post by **jclausius** » Mon Nov 05, 2007 9:56 am

Let's look at something:

A) Shut down every instance of Visual Studio .NET 2003.

B) On HKLM\SOFTWARE\SourceCodeControlProvider\, what is the ProviderRegKey value? What are the String Value Names + values for HKLM\SourceCodeControlProvider\InstalledSCCProviders.

C) Do you have any string values for "HKLM\Software\SourceGear\Vault Client" that start with "SCC"? What are the values there? Verify you have read or read/write privileges to those values within the registry?

D) Start VS 2003 .NET. Check Tools -> Options -> Source Control. Is the SCC Provider enabled? If you click SCC Provider here, and you can click Advanced, are you prompted to log into the Vault server?

thadmiller · Post by **thadmiller** » Mon Nov 05, 2007 10:30 am

A) Okay, done.

B) ProviderRegKey = "SOFTWARE\SourceGear\Vault Client"
I don't have HKLM\SourceCodeControlProvider\InstalledSCCProviders, but searching for InstalledSCCProviders I found HKLM\SOFTWARE\Wow6432Node\SourceCodeControlProvider\InstalledSCCProviders, and the only Key is "SourceGear Vault VS2003 Compatible Client" with a value of "SOFTWARE\SourceGear\Vault Client".

C) HKLM\SOFTWARE\Wow6432Node\SourceGear\Vault Client contains 2 strings that start off SCC... "SCCServerName = SourceGear Vault VS2003 Compatible Client" and "SCCServerPath = C:\Program Files (x86)\SourceGear\Vault Client\VS2003_Client\VaultIDE.dll" - and yes, I have read/write permissions to the keys.

D) SCC Provider is enabled, but Vault is not in the Source Control drop-down, and the Advanced button is disabled.

On reviewing the registry keys you had me investigate, could the issue be due to the ProviderRegKey = "SOFTWARE\SourceGear\Vault Client", yet with my system being 64-bit XP there seems to be Wow6432Node as part of the actual path?

Post by **jclausius** » Mon Nov 05, 2007 10:35 am

It could be related to something along those lines. I thought Windows itself was re-directing registry calls for this, but since VS .NET 2003 was released before the 64-bit world, it wouldn't surprise me that this is a problem.

I'll ask someone in our QA / Test team to investigate this as a possible problem.

thadmiller · Post by **thadmiller** » Mon Nov 05, 2007 1:14 pm

To answer my own question, changing the ProviderRegKey from "SOFTWARE\SourceGear\Vault Client" to "SOFTWARE\Wow6432Node\SourceGear\Vault Client" did NOT fix anything - in fact, when I loaded VS.Net 2003 I did not even have a Source Control menu item at all.