I've only used CVS myself, and have started looking at sub version. The biggest pain I have with CVS is its handling of directories, so SVN's features are certainly welcome.
A recent addition to our development team is pushing for VSS as the preferred code versioning solution. I'm really trying to gauge people's reactions, especially those people who have used both platforms. Darryl -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Spike Posted At: Friday, 23 July 2004 3:31 PM Posted To: CFAussie Conversation: [cfaussie] Re: CVS vs. VSS Subject: [cfaussie] Re: CVS vs. VSS +1 vote. I've had nothing but pain from VSS. CVS has been a much better tool in my experience and I've used it in a number of different development environments both with developers working together in the same pod and with developers scattered around the world. I've also used it with a centralized development server and I can tell you for nothing that doing that on VSS is likely to eventually get someone so mad that they'll go postal (If they're anything like the people I worked with that is). I've recently moved to SubVersion for my own stuff and I prefer it to CVS on the whole, but I haven't had a chance to use it 'in anger' where there is more than just me dealing with the repository. Spike -------------------------------------------- Stephen Milligan Code poet for hire http://www.spike.org.uk Do you cfeclipse? http://cfeclipse.tigris.org >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Sean >Corfield >Sent: Thursday, July 22, 2004 9:24 PM >To: CFAussie Mailing List >Subject: [cfaussie] Re: CVS vs. VSS > >On Fri, 23 Jul 2004 08:42:04 +1000, CFAussie ><[EMAIL PROTECTED]> wrote: >> However, I can see benefits in moving to a Visual Source Safe >> development environment, where we use a development server and >> 'centralised' development. > >What benefits can you see? I've worked with both systems and VSS was a >total dog. Corrupted files, pain-in-the-ass locking etc not to mention >being Windows-only (so we had to use Samba to share file systems since >we deployed to Unix most of the time). > >The merging stuff (with CVS) is trivial and CVS is very good at it. Of >course, you're better off organizing your workloads so that developers >aren't trampling all over each other's code anyway (that's a management >issue and if you find merging a problem, you'll find exclusive locking >even more so, in my opinion). > >I can't see *any* pros for VSS, based on my experience (and all of the >comparative literature out there - that wasn't written by Microsoft, >that is!). >-- >Sean A Corfield -- http://www.corfield.org/blog/ > >"If you're not annoying somebody, you're not really alive." >-- Margaret Atwood > >--- >You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To >unsubscribe send a blank email to >[EMAIL PROTECTED] >Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
