SCC Provider in VS2005 switching back to VSS

craigmcguff · Post by **craigmcguff** » Wed Aug 02, 2006 7:05 pm

I have installed vault 3.5 and upgraded a VSS (8?) repository. This all worked perfectly.

Loaded vs2005, set the SCC provider in options to vault, connected to the server and pulled files into my working folder - all working great.

If I exit VS and restart, when I open the solution (web) it is attempting to connect using sourcesafe and not Vault.

I have looked in the solution file and the provider is set to vault.

Where else should I look?

lbauer · Post by **lbauer** » Thu Aug 03, 2006 5:53 am

Was your project previously bound to VSS? Binding information is stored in the project files, so just changing the source control provider won't change the binding information.

You can try using the Change Source Control command under File->Source Control to unbind the project, then rebind the project to Vault.

Or you could try a fresh open from source control in Visual Studio, which should connect you to Vault and allow you to retrieve the project into new working directories.

craigmcguff · Post by **craigmcguff** » Thu Aug 03, 2006 3:29 pm

If I open the solution file in notepad I can see the following:
SccProvider = "MSSCCI:SourceGear Vault Client"

There is also a .vssscc file and a mssccprj.scc file

When I open the solution file I get a Microsoft Visual Sourcesafe error that the file is not found (the file being the path to the vault server).

I have tried reopening from source control several times, even deleting and recreating the solution file but I get the same problem each time.

TeamWiSE · Post by **TeamWiSE** » Mon Aug 14, 2006 6:48 am

as far as i know, you just need to delete the mssccprj.scc file(s).

Xomen · Post by **Xomen** » Mon Nov 20, 2006 6:11 pm

I'm having the exact same problem. I can't find any references in my solution to VSS and I deleted the .scc files. But every time I try to open the project it reverts back to VSS.

If I unbind VSS, switch the provider to Vault and rebind to the Vault database. That works fine.

I then save all and exit VS 2005. When I restart it, either by double-clicking the .sln file or by starting VS 2005 and loading the solution through the menu, it tries to connect to the source control database using VSS.

Where is it getting this setting?

gmshanes · Post by **gmshanes** » Wed Nov 22, 2006 11:24 am

I have the same problem, I just updated to 3.1.9 thinking that would fix it since my old version of Vault didn't support VS2005. At least I know it isn't my version of Vault now.

Xomen · Post by **Xomen** » Wed Nov 22, 2006 1:58 pm

I was able to get this working by deleting the project and virtual directory and getting everything back out of Vault. It's been OK since.

lbauer · Post by **lbauer** » Wed Nov 22, 2006 5:02 pm

I'd suggest Xomen's solution -- do an Open From Source Control to retrieve the project into a new working folder.

Be sure to delete/backup current working folders and any virtual directories.

SourceGear Support

SCC Provider in VS2005 switching back to VSS

SCC Provider in VS2005 switching back to VSS

Same problem

Problem fixed?