At work we started exploring using SVN for source control with Visual Studio as Visual Source Safe is still living in 1999 and Visual Studio 2005 doesn't seem to be anymore promising (Jeff Atwood recommends "
Anything but SourceSafe").
AnkhSVN was made to integrate with Visual Studio but wasn't the easiest to set-up...
Scott Hanselman says there is a new version out but it's still in Release Candidate and requires you to upgrade to a release candidate version of subversion too.
Anyway with SVN being open source I was looking at setting up a version control solution for my personal projects.
Lifehacker recently ran a two part series (
part 1,
part 2) in it's weekly Hack Attack column about setting up Subversion and TortoiseSVN for Windows. It also includes an optional Apache install to access files from other computers.
I followed the Lifehacker articles and installed
Subversion and
TortoiseSVN and created a couple of repositories for projects I am working on. I elected to skip the Apache install on my machine as I only develop from my laptop.
I'll tell you that it already saved my butt once this weekend...in a rare act of stupidity (OK it really wasn't that rare) I copied files into the wrong directory...it only overwrote one file. But with version control I just right clicked on the file and hit revert and pulled up the original file I overwrote...without source control I would of had to recreate that file.
I still need to figure out a backup solution that is easy and unobtrusive. I am thinking about one of those one-click backup external hard-drives. Maybe for my birthday ;)