I use VisualSVN Server on my server too and it is indeed nice and easy. I'd been running just the native SVN service previously because I was hesitant about having an Apache install next to the IIS installation. But VisualSVN Server makes this so easy and automated that there really was nothing else to configure (except a bit later anonymous access to the repository which requires a couple of config settings).

Highly recommended.

+++ Rick ---


>>>>The recent source control discussions have got me thinking, I do some work at the office, and some work at home.
>>>>
>>>>Do any of the Source Control apps out there work good for that?
>>>
>>>Subversion. You can either go through the web interface (via Apache) or they have a Windows service you can use. I'm using the service approach since I didn't want to set-up Apache. I didn't think of it at the time, but there are a bunch of free VM's available that already have that stuff set-up - I could have run that VM on one of my servers and just assigned it a fixed IP, then route traffic to it). I open a VPN to the office, but you could probably just configure the route to pass the traffic through (port 3690?) if you aren't using a VPN.
>>
>>
>>We have been pretty happy with VisualSvn Server for windows - it is easy to setup, hagood security settings, and a nice web interface. We deployed it in a very crappuy box with Windows 2008 and it is working great supporting like 30 developers.
>
>I figured I'd follow up about this. I decided I wanted to get some projects off my local machine so I decided to try installing VisualSVN on my web server (Win 2003 w/IIS/ASP.NET). It took maybe 10 minutes before I had everything up and running - very painless. No conflicts with anything, it just "worked". Very nice. I've used the old Win service and this was even easier to get up and running.