Cannot add SourceSafe Database as Visual Studio 2010 source control

Dean picture Dean · May 14, 2010 · Viewed 24.8k times · Source

My issue is that I cannot add SourceSafe Database for source control within Visual Studio 2010.

Our team was initially using VSS for source control in Visual Studio 2010. During an evaluation of TFS, I switched my source control to TFS. It will be a few weeks before a decision is made on TFS, so I needed to switch my source control back to VSS. However I'm now unable to add a SourceSafe Database in Visual Studio.

Steps to Reproduce in Visual Studio 2010: 1) Access the 'Open SourceSafe Database' form via Tools->Options->Source Control->Plug-in Settings-->Advanced or via File->Source Control 2) The list of available database is blank so I choose 'Browse'. 3) I browse to the srcsafe.ini file for my VSS database and select it.
4) I'm promted to confirm the Database Name - Click OK. 5) The database does not appear in the 'Open SourceSafe' Database form. The list of available databases is still blank.

Note that I can add the database fine outside of Visual Studio using VSS directly. However the databases I add via VSS do not appear in the Visual Studio forms.

I'm suspicious that this is related to "down-grading" from TFS to VSS which may not have been heavily tested at MS.

Any assistance is appreciated.

Answer

visual picture visual · Nov 30, 2010

I installed VS2010, then i install VSS, then i have the same problem, cant connect to my VSS it by default opens (TFS)

the suggestion here, to reinstall, dont sound good, did a bit more searching and found this:- http://social.msdn.microsoft.com/Forums/en/vssourcecontrol/thread/6c927805-bca6-445b-b406-0a0da8fa21d3

and found the easy solution that 'CletusLoomis' is looking for:

simply:- hanks for your post.

Could you please try the following steps?

  1. Open VS2010, then choose the menu: Tools->Options, then click "Souce Control"
  2. click drop-down box under text"Current souce control plug-in", use "None", rather than "Microsoft Visual Source Safe"

thats it, problem solved! :)

hope this helps someone else who found this page via google.