The issue is very much confusing to me. Like why cannot we have an internet access to the VSS database on the server , as far as I have read we need to setup a VPN and then connect to the server. I thought it would be similar to SVN Tortoise which
is very easy to configure and acess remotely.
Visual SourceSafe uses standard Win32 file I/O to access the VSS database. Over a LAN, this is architecture is not too bad. And while it can be done (opening up standard NetBIOS ports or the share through a VPN, over a WAN, this usage of VSS
Explorer can bring your system to its knees. Some have had success accessing the VSS share over a VPN, and others have not. It really depends on your overall make up of the VSS database, the network connection, etc.
For this reason there have been third party tools (like
SourceOffSite ) which let you gain access to your VSS database. Those tools changed the manner in which VSS data is transported from a VSS database to the end user.
In terms of configuration, if you will be using the VSS plugin, you will need to go to VSS 2005 and make sure you have the correct pieces installed -
Using Visual SourceSafe in Microsoft Visual Studio . Note, you will only have access to the VSS database through Visual Studio.
If you need more functionality when operating on your VSS database, you would want to look at either a VPN or move to something like SourceOffSite. SourceOffSite help can be found at
Hope this helps.
Jeff Clausius - SourceGear