Switching from Sourcesafe - What to look for in a product

Posted by asp316 on Stack Overflow See other posts from Stack Overflow or by asp316
Published on 2010-03-25T14:26:56Z Indexed on 2010/03/25 14:33 UTC
Read the original article Hit count: 400

We're looking to move off of sourcesafe and on to a more robust source control system for our .Net apps. We're also looking for scripted/automated deployments.

I'm a .Net developer (web and winforms). However, most of our development staff is RPG for the IBM iSeries and the devs use Aldon's LMI for source control and deployment. Our manager would prefer to stick with Aldon so all of our products are in the same system. However, I don't have experience with Aldon's products on the .Net side. I've used TFS and Subversion with Tortoise a bit, but not enough to recommend one or the other, especially in comparison to Aldon's product.

Does anybody have experience with Aldon's products? If so, thoughts please? Also, other than the obvious things source control systems do, are there things I should avoid or are there must haves? I'm open to any system.

A bit of background, I'm the only .Net dev in our company but I let operations do the deployments. I do want the ability to support concurrent checkouts if we hire a new dev.

© Stack Overflow or respective owner

Related posts about version-control

Related posts about visual-sourcesafe