Visual SourceSafe 2005 IDE Integration Problem with Visual Studio 2005

Question

Hi I have Visual Studio Professional 2005 installed and I just recently installed SourceSafe 2005 and It won't integrate with the Visual Studio IDE. The SourceSafe menu doesn't appear in the File menu of the Visual Studio and I cant import projects from SourceSafe, what can I do?

Thanks

Answer 1

Go to Tools->Options->Source Control->Plug-In Selection
In the combo box in that page, select the Visual SourceSafe plug-in.

Then to access the Projects already on SourceSafe you use the File->Open Project dialog, and click the SourceSafe button on the left bar of the Open Project dialog.

Answer 2

just curious I have vs 2005 pro too. did ur visual sourcesafe come with it. if not where did u get it???

Answer 3

VS 2005 Professional does not contain VSS2005.

You'll have to buy VSS2005 separately, or if you bought VS2005 with MSDN Premium Subscription you can download VSS2005 from MSDN site.

Alin

Answer 4

do I have to buy full version or the upgrade???

 

is there a place to get a trial of demo. Not sure if I need it...

 

Answer 5

There is no trial version of VSS2005. If you already have VSS 6.0 licenses I'd buy VSS2005 upgrade (it's about 270$ cheaper)

Alin

Answer 6

 Oops, I had the same problem, but had tro click "show all options" on the options screen before i could change the setting.

Answer 7

I wouldn't bother upgradding if I were you.  The product is identical to the older versions.

Answer 8

...to the untrained eye ;-)

Here is a brief list of features added/improved in VSS2005 http://msdn2.microsoft.com/en-us/library/th1ac915(VS.80).aspx

And I've put together a list of differences from the source control integration point of view http://www.alinconstantin.net/webdocs/scc/Vss6Vs2005.htm

Alin

Answer 9

Oh my God, I cannot believe how stupid it is to have a checkbox that says "Show all Options" be turned off by default, and that the Source Control option is not displayed by default. I spent 20 minutes looking for the source control options in VS 2005 and then searching MSDN and the rest of the internet without success until I found your post. That is shockingly bad interface design.

Answer 10

Hi!

Are you having any success with Visual SourceSafe?  When you are finished working with a file on VSS, and then you want to run your project to see if your problem was fixed...how do you do it?

I didn't have the Debug opition available...

thank you

Sayure

Answer 11

Me too, until I got this post. How many meeting they had to decide this crazy thing???

Ciao...

Answer 12

The same happens with VS 6.0? I can't find that "Show all Options" checkbox, where is it?

 

Thanks,

Answer 13

What do you do in the case where Tools->Options->Source Control->Plug-In Selection contains nothing but "None" in the drop-down combo box?  I cannot find a Show All Options(Settings) anywhere in VS 2005.  Microsoft really knows how to screw up.

Answer 14

 > What do you do in the case where Tools->Options->Source Control->Plug-In Selection contains nothing but "None" in the drop-down combo box?

 

Assuming you don't use an Express edition of VisualStudio, I'd install a source control provider. (Express edition of VisualStudio don't support source control integration)

If you see only "None" it probably means you have no source control providers installed or correctly registered. You should install VSS, TFS or another source control provider. With "None" selected you can only use source control with FrontPage web projects (which use a different provider, on the server machine, not on the client where VS is installed)

 

 >I cannot find a Show All Options(Settings) anywhere in VS 2005.

 

If you used VB/web profile which hides some of the Tools/Options pages you wouldn't have seen the SourceControl page - in which case there would have been visible a "Show all options" checkbox in the bottom of the dialog

Since you already see the SourceControl page it means you are not using the VB or Web projects Profile settings, and all options pages are already visible with your profile, therefore there is no need for a "Show all options" checkbox.

 

Alin

Answer 15

I'm using VS 2005 Pro and I have VSS installed on another computer.  I can see it using VS 6 and VS 7 but not with VS 8 - all from the same computer.  I read something about registering a DLL and really got the urge to return the product.  There was mention of certain items being needed in the registry.  They are there, but even so, the fact that VSS does not show up in the drop-down combo under Option\Source Control - does not make sense.  I am not going to write a DLL to use VSS.  If that is what it takes, then MS is going to lose some business.  That is simply poor product management if you ask me.

Answer 16

You don't have to write your own dlls to use VSS integration in VS....

 

> I'm using VS 2005 Pro and I have VSS installed on another computer

 

Could this be the cause of your problem? VSS needs to be installed on the same computer where VS is installed (the database can be on a different machine, but the binaries need to be local). It may be possible that you have registered ssscc.dll from a network share; VS6 and VS7 allowed loading it from a share, and scc integration might work in such scenario. However, for security reasons VS7.1 and later don't allow anymore loading dlls from network shares.

Make sure ssscc.dll (and in fact the whole VSS) is installed on the local computer, and the 2 SourceSafe MSSCCI providers should appear in Tools/Options/SourceControl/Plugins combobox. If you want to re-register manually the dll you'd have to run ("regsvr32 SsScc.dll" and "regsvr32 RemoteVssScc.dll")

 

Alin

  

Answer 17

I've always used VSS as a remote install.  It never occurred to me that there would be cause to disable that.  Especially not for a "security" issue.  This is on an internal, hardware firewalled, local LAN.  What is unsecure about that?  There is no benefit to having the db on a remote computer and the application on a local machine.  If I want to develop from multiple machines, what am I supposed to do; buy VSS for each machine?  This is unacceptable.

Answer 18

>  If I want to develop from multiple machines, what am I supposed to do; buy VSS for each machine?  This is unacceptable.

 

I'm sorry to hear that, but that's exactly what you'd have to do.

Please read the license agreement - you're supposed to have one VSS install and license on each client machine where you want to use it.

 

Alin

Answer 19

As I said; this is unacceptable.  I'm returning the product.  Thanks for your help in all this.

Answer 20

many thanks -solved my problem

Answer 21

Alin Constantin said:

>  If I want to develop from multiple machines, what am I supposed to do; buy VSS for each machine?  This is unacceptable.

 

I'm sorry to hear that, but that's exactly what you'd have to do.

Please read the license agreement - you're supposed to have one VSS install and license on each client machine where you want to use it.

 

Alin

 

That is not how the license agreement read to me.  The way I read it was that you have to have a full install for the database and the clients just need additional licenses and install using the same key as the database; however, the version of the license agreement that I read seemed to be vague and did not cover many scenarios.  I am with an education institution, so I can get the licenses for $25 and that is much cheaper than a VSS install for each client.

 

On a side note I wish MS would make their products available for download.  People should be able to download an ISO and create new media when their’s goes bad.  It is not like you can do anything without a key anyway.  If someone is going to go to the trouble of getting a pirated key then they will get the software through similar means.  MS could even make you log in to download your replacement media, so there would be no ambiguity.  Heck they could even make you type in the key for the download.  Anyway it is somewhat related to this topic, because that is why I ended up here (refered by another thread).