c++ .net projects revert to SourceSafe

joel4370 · Post by **joel4370** » Tue Apr 11, 2006 9:09 am

I recently switched our source control from SourceSafe to SourceGear Vault. I did not use the import tool, becuase we had some problems with sourcesafe. Everything seems to be fine, but on one developer's machine when certain projects are opened in .net 05 it looks for the old sourcesafe db. To solve this problem I go into tools/options and swich the souce control back to vault, then delete the working folder, and do a get latest version. It will open correctly then, but after the IDE has been closed and reopened, the same problem will occur. Thanks for your help.
Joel

lbauer · Post by **lbauer** » Tue Apr 11, 2006 9:45 am

The project on the developer's machine probably still has binding information that binds it to VSS.

Was the project added to Source Control using Vault IDE integration?

If so, the developer should probably do a fresh get of the project to clean working directories, using the File->Source Control->Open from source control command. This will create the bindings to Vault.

joel4370 · Post by **joel4370** » Tue Apr 11, 2006 11:09 am

The project was not added through the IDE. I have a specific file structure that I wanted duplicated in Vault, so I just dragged my tree into the vault client.

Opening from source control in the IDE solved the problem on one project, but we still have a project that binds to vault fine, but once you close the IDE and try to reopen the project it always looks at sourcesafe. Thoughts?

dan · Post by **dan** » Tue Apr 11, 2006 3:39 pm

Try unbinding the project (via Change Source Control), and then explicitly binding it to Vault.

joel4370 · Post by **joel4370** » Tue Apr 11, 2006 3:56 pm

When I go into SouceControl->change source control, the server is the vault server, and the server binding is correct, for some reason the project just thinks that it is in source safe, but it is actually bound to Vault. When I look in the .sln I see this line : SccProvider0 = MSSCCI:SourceGear\u0020Vault\u0020Client, and the .vcproj says SccProjectName="SAK", so I don't know why it thinks I am using source safe????

dan · Post by **dan** » Thu Apr 13, 2006 10:40 am

If there are .vssscc files in the folder, then try deleting them. It may be that they are holding onto VS source control info.

joel4370 · Post by **joel4370** » Thu Apr 13, 2006 11:12 am

I had tried deleting the .vsscc files, but to no avail. I think I have finally solved the problem by uninstalling SourceSafe off the machine that was giving us problems.