Re: Version Control Software



Brandon J. Van Every schrieb:

> Daniel Dyer wrote:
>
>> "Visual SourceSafe? It would be safer to print out all your code, run
>> it through a shredder, and set it on fire."
>
> In fairness, from 1996..1998 we used VSS 5.0 at DEC Commodity Graphics
> for 3D device driver development, with a team of 7..11 people. That's a
> relatively small project, and we never had any problems. I've heard
> many horror stories about VSS's reliability over the years, but I
> suspect these are from larger projects. I think worrying about such
> issues for a solo project is seriously overthinking the issues. VSS
> integrates very well into the Visual Studio environment. On the other
> hand, Perforce is free for a 2-user license, has equal ease of use, and
> is reknowned for its robustness. If I were still doing Visual Studio
> development I'd be doing that.
>
> As it is, I intend to try Subversion. It's clearly better than CVS by
> all accounts, although I couldn't tell you in what ways. I'm not sure
> if integration with things such as Eclipse is one of the ways.

Subversion for Eclipse = Subclipse ( http://subclipse.tigris.org/ )
I use it and it is really great. With JavaSVN installed it even works
perfect with svn+ssh repositories (better than TortoiseSVN).

For more information about the different systems look at this page:
http://better-scm.berlios.de/comparison/comparison.html
It contains a detailed comparison between 16 common version control systems
(including CVS, SVN and VSS).

Jan
.



Relevant Pages

  • Re: Alternatives to Visual SourceSafe?
    ... I suffered VSS for many years. ... specify which database to connect to from the command line) ... Most of our development team migrated to CVS and later to Subversion, ...
    (comp.arch.embedded)
  • Re: Replacing Visual SourceSafe (VSS)
    ... After years of being a SourceSafe user/administrator, ... to other version control systems. ... using checkin/checkout/get/diff functions in VSS. ... We've been using it for five years and never had a server issue (well, ...
    (comp.programming)
  • Upgrading Visual Source Safe and Visual Studio
    ... Uninstall VSS 6.0d on the Server ... Install VSS 2005 on the Server ... Install the clients and make sure VSS05 is working with Visual Studio 03 ...
    (microsoft.public.vstudio.sourcesafe)
  • Re: Visual SourceSafe considered harmful
    ... VSS uses, ... CVS is open ... >> requires that you completely relearn how to do source control. ... and Microsoft ...
    (comp.programming)
  • Re: Source Code Control
    ... I sit here wondering if all this Anti VSS propaganda out there is due to a ... cons of various source control systems (settling on ... ... Subversion repo is not fully consistent, it must mean your hardware is ... a BDB-based repository would become locked (but not ...
    (comp.arch.embedded)