Version Control
Discussion
Hi all
I'm looking for a cheap if not free version control system that I can access over my home network, or via the internet.
It doesn't have to have many features, simply be able to hold the current version of a project that I can access from anywhere with an internet (from work) or local network (my home) connection. If it integrates with VS all the better.
it's for my personal use so if you know of any commercial apps that give free single user licences that would be grand.
Any recommendations?
Cheers
Paul
edited to add - oh yes and windows based
>>> Edited by gopher on Wednesday 16th February 20:37
I'm looking for a cheap if not free version control system that I can access over my home network, or via the internet.
It doesn't have to have many features, simply be able to hold the current version of a project that I can access from anywhere with an internet (from work) or local network (my home) connection. If it integrates with VS all the better.
it's for my personal use so if you know of any commercial apps that give free single user licences that would be grand.
Any recommendations?
Cheers
Paul
edited to add - oh yes and windows based
>>> Edited by gopher on Wednesday 16th February 20:37
Perforce
www.perforce.com/
Has VS integration and you can use it for any purpose with up to 2 users, after that you need to buy a licence. Probably somewhat overkill, but will do the job reliably
www.perforce.com/
Has VS integration and you can use it for any purpose with up to 2 users, after that you need to buy a licence. Probably somewhat overkill, but will do the job reliably

I'm using Perforce commerically with my current client and it seems pretty OK. Almost certainly overkill for what you want though.
CVS with the WinCVS works pretty well too. And it's free (Open Source).
If you have Microsoft Visual Studio then Visual SourceSafe is quite adequete even though people like to bash it.
CVS with the WinCVS works pretty well too. And it's free (Open Source).
If you have Microsoft Visual Studio then Visual SourceSafe is quite adequete even though people like to bash it.
JonRB said:
If you have Microsoft Visual Studio then Visual SourceSafe is quite adequete even though people like to bash it.
Thanks Jon - I can use SourceSafe (MSDN) but I am having some issues over http (ie I just can not get it to work) We use this in work where it does the job, so I'm not bashing it, I jsut can't get it to work.
Cheers
Paul
We use SourceGear Vault. No problems at all so far, uses SQL Server as the back end data store, and it's got an automatic import from Visual Source unSafe which pulls in the whole file history. All access is via HTTP, so it's fully remote-access friendly.
It's not free, but it's a lot cheaper than much of the competition.
Cheers,
Pete
It's not free, but it's a lot cheaper than much of the competition.
Cheers,
Pete
pete said:
We use SourceGear Vault. No problems at all so far, uses SQL Server as the back end data store, and it's got an automatic import from Visual Source unSafe which pulls in the whole file history. All access is via HTTP, so it's fully remote-access friendly.
It's not free, but it's a lot cheaper than much of the competition.
Cheers,
Pete
Just being evaluating this and I think we will be switching(work wise) - great to administer, easy to use, like the fact it is not file based, integrates great with VS, cheap compared with the competition, but for 2 projects I really did not want to spend, hmmmm maybe 11 licences instead of 10
Edited to add:
Pete I've been evaluating a few products (version control) for work and need to write an assessment soon - Source Gear has come up favourite with me so far - can I ask if you trialled any other products, and if so what you thought?
Cheers
Paul
>> Edited by gopher on Wednesday 16th February 23:14
PetrolTed said:Oh yes, sorry, I forgot the requirement was for remote working. There are tools available to coerce VSS into working over the internet but it was never really intended to be used that way.
I sympathise on the VSS front. It's taken me an age to get it working with Visual Interdev and then to make it accessible from another PC on the network.
If it's concurrent development over the internet you want then CVS is pretty good. If it's good enough for the guys at SourceForge and a majority of other Open Source projects then it's probably good enough for most. And it's free.
Mark.S said:Er, eh?
I'll back the vote for Sourceforge, fantastic for a freebie (single user license).
See this:
"SourceForge.net is the world's largest Open Source software development website, with the largest repository of Open Source code and applications available on the Internet. SourceForge.net provides free services to Open Source developers."
Our development team of five plus a test team of two is using CVS.
Not only is it free, but the 'old hands' here reckon it's actually the best version control system they have used.
Three of us develop from home with CVS hosted in the office accessed via the VPN. Very efficient bandwidth usage, especially with compression flipped on in the client preferences.
All the usual concerns over file locking, conflicts, tagging, branching, etc proved unfounded and it does all these a sight better and more robustly than any other VCS we have used before.
We use both WinCVS and TortoiseCVS front ends plus the front end built into our IDE - all three have their good points. The IDE handles individual files really well, Tortoise is very friendly and we use it for everday stuff such as updates, commits, etc, and for really nasty things like branching code and finding out what files were checked in uder a particular change WinCVS seems to be easier to use. No need to pick and stick with one - we have all three installed and routinely use them all!
Not only is it free, but the 'old hands' here reckon it's actually the best version control system they have used.
Three of us develop from home with CVS hosted in the office accessed via the VPN. Very efficient bandwidth usage, especially with compression flipped on in the client preferences.
All the usual concerns over file locking, conflicts, tagging, branching, etc proved unfounded and it does all these a sight better and more robustly than any other VCS we have used before.
We use both WinCVS and TortoiseCVS front ends plus the front end built into our IDE - all three have their good points. The IDE handles individual files really well, Tortoise is very friendly and we use it for everday stuff such as updates, commits, etc, and for really nasty things like branching code and finding out what files were checked in uder a particular change WinCVS seems to be easier to use. No need to pick and stick with one - we have all three installed and routinely use them all!
I was working with a Unix wiz a year or so back on a Windows project and he set up CVS, WinCVS and VC++ integration. Took him 10 mins to set up and worked really well on a day-to-day, although a little too much command-line jiggery-pokery needed for some tasks like prune-and-graft.
Thing that got me was that it may have only taken him 10 mins to set up but I'm convinced it would have taken me a morning if I'd had to do it.
Thing that got me was that it may have only taken him 10 mins to set up but I'm convinced it would have taken me a morning if I'd had to do it.
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff


