[OT] Version Control Systems

  • Thread starter Thread starter C# Learner
  • Start date Start date
C

C# Learner

Just wondering what VCSes you people use with your VS.NET projects, and how
you find them.

Myself, I use Subversion from the command line and I'm happy with it. I
find it simple to use and flexible.

How about you?
 
Just wondering what VCSes you people use with your VS.NET projects, and how
you find them.

Myself, I use Subversion from the command line and I'm happy with it. I
find it simple to use and flexible.

How about you?
Click to expand...

Guess what? ;-)

Subversion (CLI) and Tortoise SVN (GUI). The repositories are
hosted on Unix servers. We sucessfully used CVS before, but
SVN has some key features that make our build system more
robust: transactions and consistent revision numbers.

bye
Rob
 
C# Learner said:
Just wondering what VCSes you people use with your VS.NET projects, and how
you find them.

Myself, I use Subversion from the command line and I'm happy with it. I
find it simple to use and flexible.

How about you?
Click to expand...

Was VSS and SOS for remotes, now (NT) CVS w/ Tortoise.

We have found CVS/Tortoise somewhat buggy, but working around those issues,
sufficient.

Personally, I'm not happy w/ it (or any VCS that I've ever used). For me, in
order to be a truly useful VCS, it has to be integrated into the build process
and commit (or reject) batch changes atomically on a successful trigger (e.g.
build).
 
Over the last 5 years I've worked with 4 different version control
systems:

1) Rational Clear Case. Very powerful, worked superbly for a team of
40 developers, but had a full time admin to feed and care for the
repository. Powerful branch and merging capabilities. Expensive $$$.

2) Visual Source Safe. The forgotten ugly step child from Microsoft.
No major improvements seen in 6 years. Known to eat projects at the
worst possible times. Sucks wind over a WAN.

3) CVS. Stable, runs everywhere, lots of client tools from command
line to GUIs. Works well over a WAN.

4) Source Gear Vault. I've only been using this product for 1 month.
Solid, works well over a WAN. Familar VSS interface. Haven't gotten
into many of the advanced features as yet.
 
C# Learner said:
Just wondering what VCSes you people use with your VS.NET projects, and
how
you find them.

Myself, I use Subversion from the command line and I'm happy with it. I
find it simple to use and flexible.

How about you?
Click to expand...

Same here, I use SubVersion and I like it.

But, the only other VCS I ever used is CVS, so I haven't seen much of these
tools.

Sam
 
C# Learner said:
Just wondering what VCSes you people use with your VS.NET projects, and how
you find them.

Myself, I use Subversion from the command line and I'm happy with it. I
find it simple to use and flexible.

How about you?
Click to expand...

We use subversion and TortoiseSVN. Some repositories are still in VSS, but
these projects are not updated that often, so migrating them is not an issue.
The thing I miss in subversion is the sharing feature of vss. I had to write
scripts to do that for me, but it turned out it wasn't that hard to do. I
really like the way SVN works (edit & check-in) vs. the way VSS works
(check-out & edit & check-in).

Frans.
 
C# Learner said:
Myself, I use Subversion from the command line and I'm happy with it. I
find it simple to use and flexible.
Click to expand...

Ditto. Nothing to add.

Christian
 
Back
Top