ansaurus

Question

Removing SourceSafe Integration from Visual Studio 2008

Answer 1

A:

You can usually edit the *.sln file and *.??proj file with out an problems to remove these bindings. These two files are just text files so you can open them in Notepad, Wordpad, or Visual Studio.

Just remove stuff slowly and then save and try to load.

Nick Berardi 2009-01-30 18:22:48

Answer 2

A:

Not sure if this works, but you can try:

Tools/Options/Source Control: set Current Source Control plug-in to "None"
Open the solution - hopefully it will tell you the provider is missing and give you an option to remove the bindings.

Joe 2009-01-30 18:25:17

No, this won't work when the solution is bound/connected to an SCC provider. As loading the solution will then automatically re-enable the SCC provider.

Bert Huijben 2009-02-04 02:29:58

Answer 3

+5 A:

Visual Studio stores source control preferences in the solution and project files. To switch providers, you have to first "unbind" the old provider.

Select File > Source Control > Change Source Control, select the solution and all the project files, and click "Unbind."
Save the solution.
Then you can change the provider with Tools > Options > Source Control.

Hand-editing the .sln and .proj files also works, but it's not exactly recommended.

Darcy Casselman 2009-01-30 18:27:00

This is the recommended way to rebind projects. (Implementing this option in Change Source Control is a requirement in the SCC specification). Reopening the solution is not necessary. After you unbind all projects you can switch the active SCC provider in Tools -> Options -> Source Control.

Bert Huijben 2009-02-04 02:27:27

Thanks, Bert. You're right about the restart, of course. I picked up some weird superstitions over the years dealing with Visual Studio weirdness. I'll update the answer with your suggestions.

Darcy Casselman 2009-02-04 20:13:44

Answer 4

+3 A:

Found it! MS's Help and Support site describes it, see section 2

Add a DWORD registry key at:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe\HideInVisualStudio

Set it to 1. Restart VS2008 and the SourceSafe plug-in option is gone.

2009-01-30 18:50:25

The recommended method is File -> Source Control -> Change Sourcecontrol. Then unbind the solution and all projects. When no projects are bound you can switch SCC providers in Tools->Options without automatically reloading the solution.

Bert Huijben 2009-02-04 02:29:20

ansaurus

tags:

views:

answers:

Removing SourceSafe Integration from Visual Studio 2008

related questions