Best route for an independent developer to get modern Microsoft source control?

Question

Given I'm:

• a solo developer using VS2008 Professional
• looking for Microsoft-produced source control (I'm aware there are alternatives)
• looking to get away from Visual SourceSafe 2005

Is it correct that my only option is to drop ~$8k on Visual Studio Team System 2008 Development Edition ($5,469) + Team Foundation Server ($2,799) - in order to get the TFS version control component?

Reading the answers to other related questions it looks like routes to bringing the TFS price down is to either become a Microsoft Gold Certified partner or to take advantage of the ISV Empower program. I'd welcome any comments related to these options.

The top non-Microsoft solution looks to be Subversion + VisualSVN, but I'd really like to go the all-Microsoft route if I can possibly swing it.

The reason that I'd like to go all-Microsoft is that it's my preference to first try the stock solution, and then later try the alternatives with the benefit of that experience. Also, I've had the rare positive experience with SourceSafe. Or, maybe I'm just a closet MS fanboy. :-)

Also, does the picture change at all when VS2010 comes out?

Thanks!

P.S. I'm downloading VisualSVN now to give that a shot since there's no reason not to.

Answer 1

If you qualify for BizSpark, that comes with TFS.

Answer 2

If you would say why you are so hip on getting it from Microsoft, we might better be able to help you?

Answer 3

Meh, just use git :D

Answer 4

If you are a solo developer you might not need to go the TFS way. As the product name suggests it is for teams. I suggest take a dive into source control systems like Subversion + TortoiseSVN or Mercurial + TortoiseHg. You could even use a web based source control if it fits your needs, sometime like Launchpad.net

Answer 5

Given you are an independent developer, and although I fully understand you wish to go the full-on Microsoft route, I can't stress highly enough that using one over the other won't mean as much to you at this point.

When I started using Source Control, I used VSS... much like many others on this site. After about 4 months, I quickly realized that there were many issues with it (namely, that it corrupted every 10 days or so, and that it caused my machine to lag horribly.)

I switched over to SVN and I do have to admit, I'm quite happy with the outcome. When you build your devleopment team to 2,3,4,5... then look into the expense. You'll find that you can get the same affect of Team Suite if you integrate SVN with something like fogbugz, or look at something like CodeSpaces

Answer 6

Give SVN a try. Look at TortoiseSVN, AnkhSVN, and Visual SVN.