SourceSafe 2005 Internet? NOT!
Let's sort out some of this stuff. My erstwhile eggheadcafe.com partner and chief geek, Robbe Morris, attempted to set this up.
I gotta tell you, this is one dude who doesn't give up easily. He is persistent, dogged, determined. Bottom line? He gave up! Mostly because it wants to hog website "#1" and we aren't gonna mess with the metabase.
He even talked to PSS and they basically said "That's what you have to do". Dudes! WebSite "#1" is not going to get changed to accomodate VSS 2005's quirks, OK?
Now let's do a little research, mostly by Googling "Sourcesafe 2005 Internet":
First big info blog: http://www.hannesschmidt.de/node/35
Prognosis: Not good. Patient might be alive, but we can't communicate with him / her....
Next Victim: http://www.yafla.com/dforbes/categories/softwareDevelopment/2005/11/24.html
Prognosis: Success, but had to workaround "Braindead configuration".
Next: http://jasonf-blog.blogspot.com/2006/01/visual-sourcesafe-2005-webservice.html
Prognosis: Moderate success, after fiddling with permissions (which should be offered during the setup process).
Next Victim: SourceSafe team's own weblog: http://blogs.msdn.com/checkitout/rss.aspx?CategoryID=5890
Prognosis: pretty spare on content! It says "We're hiring". Damn well better be hiring!
Next: Yack's blog: http://blog.davidyack.com/archive/2005/06/22/710.aspx
Link on manually registering a client.
Prognosis: Jury's still out. Yadda yadda, Warden!
Next Victim: Wikipedia entry: http://en.wikipedia.org/wiki/Visual_SourceSafe
Prognosis: Mixed review.
Oh, there is much more. I guess we will wait for the Service pack sometime late this year, or for somebody to write a whole book about it, or TFS, which certainly isn't a cheapo alternative....
I gotta tell you, this is one dude who doesn't give up easily. He is persistent, dogged, determined. Bottom line? He gave up! Mostly because it wants to hog website "#1" and we aren't gonna mess with the metabase.
He even talked to PSS and they basically said "That's what you have to do". Dudes! WebSite "#1" is not going to get changed to accomodate VSS 2005's quirks, OK?
Now let's do a little research, mostly by Googling "Sourcesafe 2005 Internet":
First big info blog: http://www.hannesschmidt.de/node/35
Prognosis: Not good. Patient might be alive, but we can't communicate with him / her....
Next Victim: http://www.yafla.com/dforbes/categories/softwareDevelopment/2005/11/24.html
Prognosis: Success, but had to workaround "Braindead configuration".
Next: http://jasonf-blog.blogspot.com/2006/01/visual-sourcesafe-2005-webservice.html
Prognosis: Moderate success, after fiddling with permissions (which should be offered during the setup process).
Next Victim: SourceSafe team's own weblog: http://blogs.msdn.com/checkitout/rss.aspx?CategoryID=5890
Prognosis: pretty spare on content! It says "We're hiring". Damn well better be hiring!
Next: Yack's blog: http://blog.davidyack.com/archive/2005/06/22/710.aspx
Link on manually registering a client.
Prognosis: Jury's still out. Yadda yadda, Warden!
Next Victim: Wikipedia entry: http://en.wikipedia.org/wiki/Visual_SourceSafe
Prognosis: Mixed review.
Oh, there is much more. I guess we will wait for the Service pack sometime late this year, or for somebody to write a whole book about it, or TFS, which certainly isn't a cheapo alternative....
We currently use SourceSafe 6.0 for our source control solution ... over a not-so-speedy (but with wonderfully high latentcy) satellite connection. We checked out SS 2005 and found it to be just as slow (even using the Internet provider as the one post noted).
ReplyDeleteOur solution has been to use Source Remoting's (http://www.sourceremoting.com/) VSS Remoting software as our client with SS 6.0 as our repository. Works wonderfully even over our abysmal connection.
We're going to be looking into SourceGear's Valut to see how well it works over a slow connection as a full SS replacement.
Why not use Subversion? Rock solid and web access works like a charm.
ReplyDeleteAgreed. When Subversion gives me SQL Server as a backend.
ReplyDelete