Cannot Add SourceSafe Database as Visual Studio 2010 Source Control

Question

My problem is that I cannot add SourceSafe Database for version control in Visual Studio 2010.

Our team originally used VSS for version control in Visual Studio 2010. During the evaluation of TFS, I switched my initial control to TFS. This will be a few weeks before deciding on TFS, so I needed to switch my original control back to VSS. However, now I cannot add the SourceSafe database to Visual Studio.

Steps to reproduce in Visual Studio 2010: 1) Access to the "Open SourceSafe Database" form using "Tools" → "Options" → "Source Control" → "Plug-in Settings" → "Advanced" or through File-> Source Control 2 ) The list of available databases is empty, so I select Browse. 3) I browse the srcsafe.ini file for my VSS database and select it. 4) I promise to confirm the database name - click "OK." 5) The database is not displayed in the form of an Open SourceSafe database. The list of available databases remains empty.

Please note that I can add the database perfectly outside of Visual Studio using VSS directly. However, the databases that I add through VSS do not appear in Visual Studio forms.

I am suspicious that this is due to a “downgrade” from TFS to VSS, which may not have been much tested in MS.

Any help is appreciated.

Answer 1

I do not believe my VS installation was damaged. I really believe that in VS 2010 there is a bug that prevents me from using VSS for version control after using TFS. Luckily for me, our team decided to go ahead with TFS for our control of the project source. I have never had to solve a problem. I believe that reinstalling Visual Studio alone would be enough to solve the problem.

Answer 2

I installed VS2010, then installed VSS, then I have the same problem, I can not connect to my VSS, which opens by default (TFS)

the suggestion here to reinstall does not sound good, it worked a little and found it: http://social.msdn.microsoft.com/Forums/en/vssourcecontrol/thread/6c927805-bca6-445b-b406-0a0da8fa21d3

and found a simple solution that is looking for "CletusLoomis":

simple: - hanks for your message.

Could you try the following steps?

• Open VS2010, then select the menu: Tools-> Options, then click on “Manage Court”
• click in the drop-down list under the text "Current Sum Control Plug-in", use "No" and not "Microsoft Visual Source Safe"

thats it, the problem is solved! :)

hope this helps someone who found this page via google.

Answer 3

My Visual Studio 2010 had very similar symptoms: selecting Visual SourceSafe 2005 in Options, I had the only menu option: Launch Microsoft SourceSafe

Following the steps described in "visual" (as of November 30'10 at 8:00 am), I found the following registry key that needs to be switched to 0 to enable SourceSafe menu options in Visual Studio 2010. After the key value registry has been changed to zero, you must restart Visual Studio and .. voila! Now I have an additional menu item Open from source control..

The registry key is as follows (for a 32-bit OS it should be slightly modified): HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SourceSafe\Namespace Extension\DisableOpenFromSourceControl

Now, why it was disabled by default, it's outside of me.

Answer 4

To do this, you must run Visual Studio 2010 as an administrator. Just click on the icon with the right button, go to "Properties", "Compatibility", on the screen of the screen that you should mark. Run this program as an administrator.

It's all. There should be some kind of file that is allowed to be shared with all users, but instead of finding the file, I prefer this solution.

Hi,

Louis Ricci

Answer 5

Your VS installation may be damaged. I would recommend uninstalling VSS, VS, and TFS, and then reinstalling VS and VSS. Unfortunately, this may take 4 hours, but this should solve your problem.

Answer 6

I had the same issue with Windows 7, Visual Studio 2010 and VSS. I noticed a few things:

• VSS as a standalone program always works on my system.
• VSS works great in my projects if the UAC level is the lowest, but not the default UAC level.

If I open the project file using the VSS control, Visual Studio will try to read the registry. It cannot read / write keys in the registry with disabled access. Therefore, I changed the permissions in the SourceSafe key registry to full access for all users. Now VSS works fine on my system with the default UAC security level.

Answer 7

I had the same problem.

I am using Visual Studio 2010, and my projects have been added to Visual SourceSafe 6.0. The VSS database list was also not requested on my machine.

After several attempts for more than 3 hours. Finally got a solution.

I am launching VS2010 using the option "Run as administrator". The list of VSS data was visible.

I think the problem may be related to registry access rights in Windows 7.

Answer 8

What a nightmare it was. Ultimately, you can set the domain or local policy.

Local Security Policy \ Security Settings \ Local Policies \ Security Settings \ User Account Control: Run All Administrators in Admin Approval Mode - Disabled

This means that any of the administrators must not have administrator permission (The Dreaded Run as Administrator). It can be installed locally, as described above or in the domain. They solved a lot of problems for us.

Answer 9

Options → Source Control → Ensure that the “Current Source Control Plugin” is installed correctly.

Mine was set up for Microsoft Visual Source Safe (Internet) and was supposed to be Microsoft Visual Source Safe.