Comments on: Someone please defend Visual SourceSafe

By: ClubPenguinCheats

ClubPenguinCheats — Fri, 21 Aug 2009 02:38:20 +0000

There are plenty of other opportunities at open-minded companies to suffer with using substandard tools.

By: Catherine

Catherine — Tue, 26 May 2009 07:04:19 +0000

I think SourceSafe is good if you work in a LAN. But the remote-access performance is terribke.

Thanks.

Catherine Sea
http://www.scmsoftwareconfigurationmanagement.com/

By: Catherine

Catherine — Tue, 26 May 2009 07:01:28 +0000

I think SourceSafe is good if you work in a LAN. But the remote-access performance is terribke.

Thanks.

Catherine Sea
http://www.scmsoftwareconfigurationmanagement.com/

By: Kevin

Kevin — Thu, 16 Oct 2008 02:58:36 +0000

If all your developers work in the same building and you do not need advanced project branch/merge feature, SourceSafe should be fine for you.

I am writing a VSS tutorial at:
http://www.kevingao.net/sourcesafe-vss-how-to

If you like VSS, you can take a look. :)

Thanks.

Kevin Gao, MCSD, MCDBA

By: Daniel

Daniel — Wed, 21 Nov 2007 19:29:54 +0000

We are finally migrating from VSS to SVN and i’m looking forward to it. My only worry is that VSS will manage to get corrupted once again before the migration… :)

Honestly VSS might maybe have in some way been a almost ok tool back in the days (not to me) but to me i don’t know how many times we’ve been working our asses of to uncorrupt the database, fix incorrect permissions and so forth…

By: Josh Stodola

Josh Stodola — Fri, 02 Nov 2007 01:09:28 +0000

I don’t mind it. We use it at work and it’s not that bad. Being able to compare history versions right in Visual Studio is pretty sweet. Sometimes I am just like “Hmm, lets see who wrote this line of code”. It was painful to get it setup, but now it’s cake.

I haven’t used anything else extensively, so my opinion is somewhat biased. Its an opinion nonetheless.

By: owen

owen — Mon, 29 Oct 2007 03:25:30 +0000

I used VSS when i first got into development, didn’t mind it, then I tried to push everyone into continuous integration only to find that because of various bugs in VSS the repository would become frequently corruped and needed rebuilding/scanning. So we switched to SVN and not one of us looked back. It’s fine, but really not great. Especially when you look at the competition.

By: Sasha Sydoruk » Someone please defend Visual SourceSafe

Sasha Sydoruk » Someone please defend Visual SourceSafe — Mon, 29 Oct 2007 02:54:39 +0000

[...] Someone please defend Visual SourceSafe. [...]

By: Rob Prouse

Rob Prouse — Tue, 11 Sep 2007 19:41:47 +0000

I am using TFS at work with a small team and a very large project. For the most part it works very well, but every so often we hit one of those boundary conditions (usually around branching/merging or backing out changes) and it can get very difficult to get it to do what you want. It is a good product, but I would recommend waiting for the next version before migrating.

We were using VSS for this project before and it was nothing but painful. Our project is so large that we had regular corruption of the repository, we couldn’t branch, if different developers had different versions of VSS installed it caused problems with encodings. It was like night and day when we switched to TFS despite the problems.

I use SVN at home with TortoiseSVN and the VisualSVN plugin for Visual Studio. It just works and I never have any problems with it.

By: Poul R. Hansen

Poul R. Hansen — Wed, 22 Aug 2007 06:07:54 +0000

Actually I wouldn’t touch SVN nor VSS if I could avoid it, TFS is simply way to nice, the only thing missing from TFS is the ability to “mirror folders”, not branch them, but an actually mirror where the mirror is as much the real thing as the original, and changes in one of the mirrors will also change the original.