I’ve long been a big fan of VisualSVN because of how well it integrates with Visual Studio and because it’s a relatively light-weight source control solution. If you’re familiar with Tortoise SVN, then you know what I mean.
So, I was delighted to learn about the new 3.0 version with added support for Visual Studio 2012 and the new Community License that is free for commercial use. This is great for freelancers and student developers. BUT WAIT! There’s a catch. Turns out you can only use the free version on computers that are not part of an Active Directory domain.
Did you get that last part? Hello?
Now, I love the fact that the folks at VisualSVN are providing a free community license. Great idea. But this restriction effectively eliminates any community benefit for the thousands of SharePoint developers that are perfectly happy using SVN. Come on, guys! In order to do any serious SharePoint work, you need a VM that is configured to use – say it with me – Active Directory! For SharePoint 2013, it’s an absolute must.
Oh well…the dark side is beckoning. Can you say “TFS”?