How do I replace or reconfigure my Team Build server if I switch to Mercurial

I'm considering moving from TFS source control to Mercurial with HgScc. How do I replace the Team Build server aspect of my Team Foundation system or reco开发者_开发百科nfigure Team Build to use Mercurial to pull the newest branch? Currently all of our released to production binaries are build on our build server to prevent workstation specific changes, libraries, settings, etc from creating incompatible builds, keeping release builds from tying up workstations, and generally for quality control. How do I do this if I switch our C# .NET development to a Mercurial based version control system?

I don't believe you can continue to build with TeamBuild without some pretty ugly hacks. I would recommend looking at either:

• TeamCity from JetBrains. I love this product. It's free for smaller usage, with commercial options.

• CruiseControl .net - Used this before moving to TeamCity, worked fairly well but it's been a few years for me.

  I applaud your desire to do builds off of your dev machines - really the best way to go in my opinion.