tags:

views:

42

answers:

1

I have started a new job, where one of my first responsibilites is to import an ASP codebase previously maintained by an agency and now being taken in house. This codebase is currently stored in a Perforce repo.

My new company has a single Subversion server running on a Windows XP desktop machine. This is used by some of their internal developers as a basic code repo for small projects.

I have the opportunity to create an entirely new source control server for the company's entire codebase.

Once I have imported and got their developers running on their ASP codebase, I will also be commencing a new project, in C#, using Visual Studio which I will also wish to keep under source control.

I am completely open to any solution. We have a VMWare environment here, so anything's possible. I'd like to be able to import the history from Perforce using a tool if possible. I'd like good integration with Visual Studio, but there should be a standalone client or shell integration for developers not using VS.

Most of the company's developers do not currently use source control, so it's probably going to be a slightly uphill battle to persuade people of its benefits - thus, 'friendlier' solutions might be better recieved.

Cash is not necessarily a problem, but obviously cheap or free is a plus.

I have limited exposure to implementing source control solutions (although I'm an enthusiastic user of them), so any suggetions or comments are gratefully welcomed.

Many thanks in advance.

+2  A: 

If your new company has a Subversion repository already, I suspect they're already familiar with this.

I think that's a good reason in itself to go with Subversion (barring any features it's missing which are essential). Otherwise you're going to introduce another tool, developers will face a (possibly small) barrier of having to learn both, plus you'll require an administrator to look after both. I find there's an enormous benefit in teams using the same tools (even at the expense of missing a few features).

Brian Agnew
They should just move that on a server (i.e. do regular backups, monitor the disk health, etc)
Aaron Digulla
I agree - and that's what I'm currently thinking; however there are only three developers (working on seperate projects to the ASP codebase ones) that use this server.I realise I could just virtualise the machine as-is, however this wouldn't solve the problem of the OS being WinXP and the installation itself not being ideal.If we abandon the idea of using the server itself, and also accept that the developers I want to persuade don't currently use it, we're back at the beginning with an open field.So yes, it's a good reason but I am interested in hearing alternatives.
Jamie