Source Control, what do you use ?

[Necuno]

apart from ms source safe 2005 what else can one use which is a lot better ?

 

[MielieSpoor]

TFS. I don't really think there is better, but it comes with a price tag. If you don't really have a lot of projects then this won't be worth it. Your team size and amount of projects really determines the source control you use.

For TFS you need atleast 15 devs to work on Source Control and have a fair amount of projects you need to administer...

 

[davemc]

I use subversion.
Lots of open-source administrators still use SVN, and, yup, it still works.

Neither have given me any problems and are feature rich.
But, Source-Safe gave me grey hairs.

 

[CorneN]

Me and a friend from Germany work on the same C++ project using Eclipse editor and CVS that comes with it. That works pretty well, though I must say that I have not had any experience with other source control apps.

 

[Nerfherder]

I use subversion.
Lots of open-source administrators still use SVN, and, yup, it still works.

Neither have given me any problems and are feature rich.
But, Source-Safe gave me grey hairs.

+1 For subversion

unfortunately we are forced to use a product called Serena Dimentions, its horrible and really lets you down when you need it to work.

 

[Nod]

Subversion + webSVN + TortoiseSVN.
Can't go wrong with that.

 

[dequadin]

For Windows + Visual Studio I use:
Visual SVN + AnkhSvn

For non Visual Studio Stuff I use TortoiseSVN as my client, but the same VisualSVN repository.

All are free and brilliant...

 

[Saajid]

I use Subversion with Tortoise SVN.

Why on earth would any of you be using SourceSafe? Why subject yourself to such torture?

Eric Sink says it best:

Bottom line: If you are still using SourceSafe, Vault 5 will remove your last excuse.

In fact, shortly after Vault 5 is released, I plan to go on a world tour. If you are still clinging to SourceSafe, I will visit your office. I will taunt you mercilessly and suggest an MRI to confirm that there is nothing between your ears but bone. And I will drench you with my new Super Soaker Max Infusion Flash Flood Water Blaster.

And I will be morally justified. You've been given many opportunities to switch to any one of several dozen competent version control tools. And yet, it's 2009 and you're still using SourceSafe. Surely you didn't expect this to end well?

Source: http://www.ericsink.com/entries/vault5_beta2.html

 

[rrh]

+1 for Subversion (as the repository). Client-side: use AnkhSvn & TortoiseSvn.

NB: stick with the directory structure recommended in the [free] Subversion manual / hundreds of articles on Subversion. Apart from working well nearly every article on Subversion expects this layout; sticking to the structure makes following instructions that much simpler when you are trying something new.

There are numerous articles on installing Subversion. The following is a good starter: http://www.codinghorror.com/blog/archives/001093.html

Finally, if you are installing Subversion, consider going continuous integration with Cruise Control. You will never look back.

 

[rrh]

In fact, shortly after Vault 5 is released, I plan to go on a world tour. If you are still clinging to SourceSafe, I will visit your office. I will taunt you mercilessly and suggest an MRI to confirm that there is nothing between your ears but bone. And I will drench you with my new Super Soaker Max Infusion Flash Flood Water Blaster.

Source: http://www.ericsink.com/entries/vault5_beta2.html


Eric is a blast. His how-to on source control should be compulsory reading for programmers: http://www.ericsink.com/scm/source_control.html

 

[SQLGuru]

Subversion + TortoiseSVN

no hassles at all. Easy to set up, easy to maintain, and free!

 

[shogun]

Visual SVN for the server, Tortoise for the client - and Ankh for Visual Studio integration.

Worked with SourceUnsafe for too many years... doubt i'll ever go back when VisualSVN is sooo easy to set up and use.

 

[Veroland]

apart from ms source safe 2005 what else can one use which is a lot better ?

You mean source UNsafe

I use SVN and I set it up to use apache2 webdav for HTTP and to auth agains my LDAP directory.

 

[dequadin]

You mean source UNsafe

I use SVN and I set it up to use apache2 webdav for HTTP and to auth agains my LDAP directory.

If you use VisualSVN it takes care of all that (Apache + LDAP integration).

Makes installation a lot easier. Of course if you like editing config files, you can use the Windows build of CollabNet Subversion Server

 

[Veroland]

If you use VisualSVN it takes care of all that (Apache + LDAP integration).

Makes installation a lot easier. Of course if you like editing config files, you can use the Windows build of CollabNet Subversion Server

All my stuff at the office run on Linux and AIX. The LDAP structure is also custom and I have all the other stuff authenticating there, Jabber etc

 

[icyrus]

Mercurial

 

[Veroland]

O yes, at the client I'm sitting at currently they use Clearcase - which in my opinion is a pain in the @ss

 

[dequadin]

All my stuff at the office run on Linux and AIX. The LDAP structure is also custom and I have all the other stuff authenticating there, Jabber etc

OIC.

When I first set up SubVersion, I used the CollabNet build and it was painfull. VisualSVN is my kinda thing: next-> yes -> next -> next -> done!

I don't want people to suffer unnecessary

 

[Veroland]

OIC.

When I first set up SubVersion, I used the CollabNet build and it was painfull. VisualSVN is my kinda thing: next-> yes -> next -> next -> done!

I don't want people to suffer unnecessary

I'm a bit of a terminal person myself. yes yes, I know, everyone has their flaws!

 

[malec]

svn and git