Comments on: Visual SourceSafe: A Public Service Announcement http://blog.uncommons.org/2008/05/23/visual-sourcesafe-a-public-service-announcement/ Rants and opinion interspersed with awe-inspiring tales of heoric software engineering endeavours. Wed, 19 Nov 2008 14:13:49 +0000 http://wordpress.org/?v=2.6.3 By: Dew Drop - May 27, 2008 | Alvin Ashcraft's Morning Dew http://blog.uncommons.org/2008/05/23/visual-sourcesafe-a-public-service-announcement/#comment-1544 Dew Drop - May 27, 2008 | Alvin Ashcraft's Morning Dew Tue, 27 May 2008 12:01:43 +0000 http://blog.uncommons.org/?p=81#comment-1544 [...] Visual SourceSafe: A Public Service Announcement (Dan Dyer) [...] [...] Visual SourceSafe: A Public Service Announcement (Dan Dyer) [...]

]]> By: Tom Pridham http://blog.uncommons.org/2008/05/23/visual-sourcesafe-a-public-service-announcement/#comment-1539 Tom Pridham Mon, 26 May 2008 23:07:54 +0000 http://blog.uncommons.org/?p=81#comment-1539 VSS was a good tool in the era of 1999 / 2000. VSS had it's issues, but was better than not using version control at all. I am not a fan of CVS, but I really like subversion. I have seen some projects crash and burn because they did not use any type of version control. So VSS is better than nothing, but most version control packages now are all better than VSS. Regards, Tom Pridham VSS was a good tool in the era of 1999 / 2000. VSS had it’s issues, but was better than not using version control at all. I am not a fan of CVS, but I really like subversion.

I have seen some projects crash and burn because they did not use any type of version control. So VSS is better than nothing, but most version control packages now are all better than VSS.

Regards,
Tom Pridham

]]> By: Rodger http://blog.uncommons.org/2008/05/23/visual-sourcesafe-a-public-service-announcement/#comment-1538 Rodger Mon, 26 May 2008 22:52:42 +0000 http://blog.uncommons.org/?p=81#comment-1538 I think the view from MS is to use (if your going to) SourceSafe as a starting point for the single developer or perhaps a small team/project as a stepping stone to move towards Team Foundation Server. I am fairly positive even Microsoft wouldn't recommend it for use on larger teams or mission critical projects. VSS 2005 with the appropriate patch works fine to that end. People freak though when they see the cost involved with TFS. Although with the existence of many single-developer/small team version control systems for free, it's really not needed. Perforce I believe offers such a version? As does Vault. Both of which would most likely be a better choice. Subversion can be a decent choice with TorrtiseSVN + VisualSVN, Doesn't feel nearly as integrated as something like VSS and TortiseSVN certainly has one of the worst context menu systems I've seen in quite some time. I guess overall, I see VSS in relation to TFS as I see Access to SQL Server. Some people seem to use Access for large insane projects for which it was never intended. I think the view from MS is to use (if your going to) SourceSafe as a starting point for the single developer or perhaps a small team/project as a stepping stone to move towards Team Foundation Server. I am fairly positive even Microsoft wouldn’t recommend it for use on larger teams or mission critical projects. VSS 2005 with the appropriate patch works fine to that end. People freak though when they see the cost involved with TFS.

Although with the existence of many single-developer/small team version control systems for free, it’s really not needed. Perforce I believe offers such a version? As does Vault. Both of which would most likely be a better choice. Subversion can be a decent choice with TorrtiseSVN + VisualSVN, Doesn’t feel nearly as integrated as something like VSS and TortiseSVN certainly has one of the worst context menu systems I’ve seen in quite some time.

I guess overall, I see VSS in relation to TFS as I see Access to SQL Server. Some people seem to use Access for large insane projects for which it was never intended.

]]> By: Blake http://blog.uncommons.org/2008/05/23/visual-sourcesafe-a-public-service-announcement/#comment-1536 Blake Mon, 26 May 2008 21:12:58 +0000 http://blog.uncommons.org/?p=81#comment-1536 "They don’t teach source code management in universities (despite it being arguably the most important tool for professional software development)." They taught us CVS and SVN at the University of California, Irvine. “They don’t teach source code management in universities (despite it being arguably the most important tool for professional software development).”

They taught us CVS and SVN at the University of California, Irvine.

]]> By: Brian http://blog.uncommons.org/2008/05/23/visual-sourcesafe-a-public-service-announcement/#comment-1534 Brian Mon, 26 May 2008 20:53:18 +0000 http://blog.uncommons.org/?p=81#comment-1534 Lol, I too once thought VSS was good. Ah the innocence of youth. I experienced every one of those "features" you mentioned and I laugh about them now. I can't believe people out there still use VSS.... Lol, I too once thought VSS was good. Ah the innocence of youth. I experienced every one of those “features” you mentioned and I laugh about them now. I can’t believe people out there still use VSS….

]]> By: Dan Howard http://blog.uncommons.org/2008/05/23/visual-sourcesafe-a-public-service-announcement/#comment-1532 Dan Howard Mon, 26 May 2008 19:56:38 +0000 http://blog.uncommons.org/?p=81#comment-1532 I recently had this discussion with one our company partner's developers. He said the new VSS 2005 is much better. Whatever that means. I never used the new version but the old one VSS from Visual Studio 6 has other pooines as well. It merges on commit and creates directories in UPPER case when you import. Total garbage - and it is sad that people still use and defend this junk. I recently had this discussion with one our company partner’s developers. He said the new VSS 2005 is much better. Whatever that means.

I never used the new version but the old one VSS from Visual Studio 6 has other pooines as well. It merges on commit and creates directories in UPPER case when you import. Total garbage - and it is sad that people still use and defend this junk.

]]> By: GrokCode http://blog.uncommons.org/2008/05/23/visual-sourcesafe-a-public-service-announcement/#comment-1531 GrokCode Mon, 26 May 2008 17:40:43 +0000 http://blog.uncommons.org/?p=81#comment-1531 Ughhh Source Safe. Just hearing the name brings back terrible memories. Repository corruption before big milestones. Loosing history rebuilding the repository. Again. Its the most benighted pile of steaming garbage I've ever had the misfortune to work with. Ughhh Source Safe. Just hearing the name brings back terrible memories. Repository corruption before big milestones. Loosing history rebuilding the repository. Again. Its the most benighted pile of steaming garbage I’ve ever had the misfortune to work with.

]]> By: Daily del.icio.us for May 20th through May 24th — Vinny Carpenter’s blog http://blog.uncommons.org/2008/05/23/visual-sourcesafe-a-public-service-announcement/#comment-1523 Daily del.icio.us for May 20th through May 24th — Vinny Carpenter’s blog Sat, 24 May 2008 22:01:01 +0000 http://blog.uncommons.org/?p=81#comment-1523 [...] New Adventures in Software » Visual SourceSafe: A Public Service Announcement - “Visual SourceSafe? It would be safer to print out all your code, run it through a shredder, and set it on fire.” - (Attributed to an unidentified Microsoft employee). [...] [...] New Adventures in Software » Visual SourceSafe: A Public Service Announcement - “Visual SourceSafe? It would be safer to print out all your code, run it through a shredder, and set it on fire.” - (Attributed to an unidentified Microsoft employee). [...]

]]> By: evensonic http://blog.uncommons.org/2008/05/23/visual-sourcesafe-a-public-service-announcement/#comment-1508 evensonic Fri, 23 May 2008 21:40:56 +0000 http://blog.uncommons.org/?p=81#comment-1508 I agree 100%. I've been amazed for years that you don't see more rants against VSS. Hopefully it's because VSS simply does not register on most developers' radar. But the evils of VSS must be told to help save the naive from thinking it is a legitimate choice for version control. I agree 100%. I’ve been amazed for years that you don’t see more rants against VSS. Hopefully it’s because VSS simply does not register on most developers’ radar. But the evils of VSS must be told to help save the naive from thinking it is a legitimate choice for version control.

]]>