VSS import worked, but VS confused between Vault and VSS

[hmerrill123]

I'm currently evaluating Vault as a VSS alternative.

My enviroment is
Windows XP (my machine) - VSS client installed
Visual Source Safe 8.0.50727.42 installed on MS Windows 2003 server
Visual Studio 2005

I recently installed on my Windows XP box
MS SQL Server 2005
Vault 3.5.1 Server, Admin, Client, Source Safe Import

I successfully used the Source Safe Import tool to import a VSS database into Vault. Then in Visual Studio 2005, I did

1. "unbind" on all the VSS bindings, and then
2. changed Source Control Provider from VSS to Vault, and then
3. went to "Change Source Control" and re-bound the solution
and projects to the new Vault repository.

Everything looked good. I right clicked the solultion, did Clean, Get Latest, and Rebuild - still everything looked good. So I closed the solution, then re-opened it and the source control provider had changed back to Visual SourceSafe - and all the bindings were invalid (because they were looking at the Vault repository website).

I've tried this several times and every time it reverts back to Visual Source Safe. What am I doing wrong, or not doing right??

Thanks for any help!

[Beth]

Try going into the Vault GUI and setting it to be the default source control provider. That would be under Tools - Options - General and is the last option listed.

[hmerrill123]

Tried that, but again when I closed the solution and then opened it back up, it switched back to Visual SourceSafe - even though the Default SCC Provider was checked in the Vault client.

Any other ideas?

[Beth]

Are you opening the project from disk or opening Visual Studio first and then opening the project?

Try this.... Open Visual Studio first. Go to Tools - Options - Source Control and set it for Vault. Then see if your project is listed in recently opened.

Let me know what it does.

[Beth]

Another thing you might want to do is check this registry key to see if Vault is set there:

HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider

[kreester]

I was able to set Vault as the default in VStudio by doing the following (I don't think the switch in the Vault client is setting the correct registry key for VStudio 2005):

locate the key CurrentSourceControlProvider under HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0

change ProviderRegKey to SOFTWARE\SourceGear\Vault Client

Things became a lot cleared after I made this change.

[mserfass]

I'm having this same problem. No matter how or where I set the source control provider it keeps reverting to VSS.

I went through the same steps as hmerrill123. I set the "Make Vault your default SCC Provider" option in Vault Client. I changed it in VS 2005. I reset bindings a few times. I repeated these steps in every permutation of the order of actions I can think of. Same problem.

The HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider setting was set to SOFTWARE\SourceGear\Vault Client.

HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\CurrentSourceControlProvider was set to Software\Microsoft\SourceSafe, so I changed it to
SOFTWARE\SourceGear\Vault Client. I closed VS2005 before I made this change. After I changed the key I opened VS2005 and checked the source control settings. It was set to SOFTWARE\SourceGear\Vault Client. I opened the project, but I got the "Unable to Access Database" prompt again. I checked the source control settings of VS2005 again, and it was back to VSS. I rechecked the HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider setting, and it was back to Software\Microsoft\SourceSafe. The (Default) setting is set to {53544C4D-FFD5-48A9-B04A-0700CCD31070}. Does that make a difference? I tried deleting the guid, but that only made VS2005 set source control to none. I switched it back to Vault, and it reset the guid.

I don't know what else to change. I have a team of developers preparing to switch from VSS to Vault. Do I have to tell them to change registry settings? Do they have to rebind every time they open a project? This will prevent us from switching. I really need a solution to this.

I'm opening VS2005, then opening the project from within VS2005. I'm using Vault 3.5.2, connecting to Vault services on the localhost. Windows XP SP2, SQL Express 2005 SP2, VS 2005 SP1, .NET Framework 2.0.

[lbauer]

There may still be binding information that has the project pointing to VSS as the SCC provider.

Here are some tips when opening items that have been imported from VSS, from one of our KB articles:

If you have already imported the project to Vault but it is bound to VSS, and you don't want to re-import the project, you can:

First, backup the project on your local machine. You want to do the following steps with a fresh working directory:

1. Attempt to open the project from Vault with VS 2005 using File->Source Control->Open from Source Control (it will fail)
2. Go to the Change Source Control dialog and unbind the solution/project. It may take a few tries, and you may need to exit and re-enter Visual Studio before it gets unbound correctly.
3. Depending on your projects and setup, you may need to checkin the unbound versions of the project/solution files to Vault.
4. Using Change Source Control, now attempt to bind the project to Vault and checkin the changed solution/project files after they are correctly bound.
5. Other users should now open the project from Source Control (see step 1). This should succeed if the VSS bindings have been removed.

[mserfass]

That did it! Thanks! Now I am able to open the solution file directly in VS 2005 (rather than open from source control). It also worked on a second machine. On the second PC I opened from source control into a new, empty folder. I was able to open the solution directly from VS 2005 there as well.

[lbauer]

Great! Thanks for the update.