Web Development

General discussion


What version control app are you using?

By SteveGoss ·
I'm at a small company considering a software version control and library management package. We are doing traditional code development for embedded applications.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

why not

by Jaqui In reply to What version control app ...

use the one supported by your development tools?
most commonly, still, is pcvserver.

Since I'm on linux, I have 3 currently installed.

Collapse -

Depends on requirements

by The Ref In reply to What version control app ...

* If integration with Visual studio is important use Visual Source Safe
* If you want continuous integration use Subversion, which is free.
* On really large projects use Clear Case (but it takes a lot of maintenance and costs a lot)

Collapse -


by Dragon Emperor In reply to What version control app ...

My company uses SourceGear Vault. It is more robust than SourceSafe, faster over remote connections and still integrates very nicely with Visual Studio.

Collapse -


by onbliss In reply to What version control app ...

We had some Visual Source Safe integration issues with VB6, that seemed to be sorted out well in VS2003. Now with VS2005, the newer version of VSS seems to be doing quite well. I have not yet integrated it with VS2005, we are evaluating Team Foundation Server further.

My friends are using VSS for PowerBuilder files, SQL Server SQLs, MS Access databases.

Collapse -

You Need To Assess Your Expectations

by stew In reply to What version control app ...

There are many different tools available and they take different tacks on controlling your content. Some are more efficient than others. Some support remote users and others don't. Some are command line only, some are GUI only, and some provide both. Among those that provide both a CLI and a GUI, there are some that provide only some functionality through the CLI, while others go so far as to implement the GUI in terms of the CLI.

If you want file-by-file control, tools like RCS, CVS (based upon RCS), Subversion (based upon CVS, I think), and SourceSafe work fine. The problem with that approach is that such tools don't provide the means to treat a group of changes across multiple files as an atomic change to the repository. Tools that provide change level control, such as Perforce and, I think, ClearCase, allow you to check in changes to multiple files as an atomic change. Others can then extract that set of changes atomically.

You have to consider cost, too. Some products are really expensive and others are free. Some require a server; others don't. A few even dictate process.

I've used SCCS, RCS, MKSSI, Visual SourceSafe, another Windows-based program I can't recall the name of, and Perforce. The one I can't recall was sluggish, but provided the best mix of features, as I recall, but that doesn't help you! Among the rest, Perforce is clearly better, though it does have some quirks.

I know I've caused you to ask yourself more questions than given you answers, but I hope I've helped you understand things to look at when comparing options.

Collapse -

I take it you haven't actually used Subversion.

by apotheon In reply to You Need To Assess Your E ...

Your statement to the effect that you can't make a change to a number of files as a single update to the repository is inaccurate. I can't really speak for RCS or CVS, since I've used neither.

My preference for version control is a Subversion repository using FSFS and SVK for local version control and repository access. SVK is a really nice system.

Subversion has a couple of Windows clients, including TortoiseSVN, which integrates with the file browsing capabilities of Windows Explorer seamlessly.

Collapse -

I Listed Those I Have Used

by stew In reply to I take it you haven't act ...

It wasn't hard to surmise that I hadn't used Subversion since I listed those I have used and Subversion wasn't on the list.

Apparently, my assumption was wrong regarding Subversion. I assumed that since it was based upon CVS/RCS, it used a file-by-file approach. I should have left it off of that list since I didn't know. I"m sorry for the confusion.

Related Discussions

Related Forums