Re: Running SourceSafe on remote webserver
- From: "Mike {0A6FF490-CF84-4d78-BD85-FF011A0C310C}" <TechGuy@xxxxxxxxxxxxxxxxx>
- Date: Mon, 11 Feb 2008 21:19:50 -0800 (PST)
Alan Constantine's home page describes how to set this up:
http://alinconstantin.homeip.net/webdocs/scc/VSS_Internet.htm
But note there are some REALLY IMPORTANT items missing from his
instructions (unless he's updated it recently). To save you a BUNCH
of grief, here they are:
- Each client user must have a Windows user account on the server (or
an account in AD if your server is using AD).
- Each client must *also* have a VSS account set up on the server.
- The VSS user account must be named EXACTLY like the Windows account
name for the user.
- The VSS user account PASSWORD must be EXACTLY like the Windows
account password.
- When you create the Windows user account(s), make sure you set them
so the passwords don't expire and so that the user is not required to
change it on first log in.
- You must give each VSS user full read/write permissions on the
folder that contains the VSS database.
- You need an SSL certificate on the server for secure
communications. It will NOT work over HTTPS without a valid SSL
certificate!!!!
- You must access the VSS services via an HTTPS URL (secured URL). I
would NOT do this without a secure connection!!! (not even sure if you
CAN).
- When accessing VSS server from VSS client over HTTP, you will have
frequent write failures. Use the VSS client only for simple stuff
like browsing projects, comparing versions, and labelling. Do NOT use
it for transferring large quantities of files in or out of the
server. It's EXTREMELY unreliable over HTTP(s).
- If you use the VSS client, you must set up a "net use" to the
path... something like: net use \\mydomain\myvssfolder /
user:myvssusername *
- Yes, you can do this with the VSS share over HTTP. Setting up
your server creates a web folder, which you can "net use" across the
internet... You can even browse if via Windows Explorer and any
Windows application... It's just like connecting to a network share.
- To access the VSS server over HTTPS from Visual Studio, you do NOT
need to connect to a network share. File transfers between Visual
Studio and VSS over HTTP seem to be totally reliable, unlike transfers
between the VSS client and the server over HTTP(s).
- When setting up your connection from within Visual Studio, it's
confusing... REALLY confusing. After you point to the server via
something like \\mydomain, then the path is \\localhost\myvssfolder.
Seems odd, but you do have to reference the server as if you're
locally on it.
- You will frequently get $8000005 errors because for some reason, the
HTTPS service on the server isn't responding for VSS requests. You'll
have to remote control the server and bounce (restart) the HTTPS
service. If you're running web sites on that same server, this will
reset those web sites and lose any open sessions.
- You may time out when going to the pending checkins tab in Visual
Studio if you have a medium or larger solution. This may also happen
if you're checking in a bunch of files. VSS over HTTP(s) is way way
slower than over a LAN with a UNC connection.
- Lastly (or firstly), you need to tell Visual Studio to use VSS over
HTTP (tools, options, source control, change the drop down to
"Microsoft Visual SourceSafe (Internet)".
Hope this helps and GOOD LUCK! You're going to need it! You'll find
that there's virtually ZERO help out there for this type of set up.
Apparently, very few people are doing it, and I'm betting it's because
it's so difficult to find informatoin on setting it up properly.
Sometimes I think that I and Alan are the only 2 people on the planet
using this feature... and I'm not so sure he's actually using it this
way.
--------------------------
Owner/Operator of
www.MichaelsAttic.com
On Feb 11, 3:37 pm, engwar <engw...@xxxxxxxxx> wrote:
We're running SourceSafe on an internal server at my company but have
been asked to look into running the server component on a webserver
outside of our corporate network. We would use either Visual Studio or
the SourceSafe client application to check files in/out.
+ Does SourceSafe allow the hosting of the server component somewhere
other than the local network? (when I choose 'Add SS Database' the
verbiage implies that the ini file I'm looking for is on the local
network.)
+ Would the source code be available only to people whom we've set up
as users or does hosting it outside of our firewall basically publish
our source code?
.
- References:
- Running SourceSafe on remote webserver
- From: engwar
- Running SourceSafe on remote webserver
- Prev by Date: Running SourceSafe on remote webserver
- Next by Date: Re: Migrate Source Vault to VSS 2005
- Previous by thread: Running SourceSafe on remote webserver
- Next by thread: Re: Running SourceSafe on remote webserver
- Index(es):
Relevant Pages
|
