If TeamCity is working for you, I'd suggest studying testing first. One of the major values in continuous integration is automated test-running. I can recommend a book on that: The Art of Unit Testing with Examples in .NET.
My personal opinion is that MSBuild scripts are best left to Visual Studio. If having TeamCity run solutions and NUnit/xUnit tests proves insufficient, you might take a look at NAnt. While it is XML-based, I find it easier to understand than MSBuild.
发布评论
评论（1）
我认为 TeamCity 走在正确的道路上；我们首先尝试了 CruiseControl.NET，发现它需要更多的 XML 编辑。
有一本关于.NET 中的持续集成的书；我还没读过。
还有持续交付：通过构建、测试和部署自动化实现可靠的软件发布 - 我也没有读过，但福勒认可的书籍通常都很优秀。该系列中还有一本关于持续集成的旧书。
如果 TeamCity 适合您，我建议您先学习测试。持续集成的主要价值之一是自动化测试运行。我可以推荐一本关于这方面的书：The Art of Unit Testing with Examples in .NET 。
我个人的观点是，MSBuild 脚本最好留给 Visual Studio。如果证明让 TeamCity 运行解决方案和 NUnit/xUnit 测试还不够，您可以查看 NAnt。虽然它是基于 XML 的，但我发现它比 MSBuild 更容易理解。
You're on the right track with TeamCity in my opinion; we tried CruiseControl.NET first and found it required more XML-editing.
There is a book on Continuous Integration in .NET; I have not read it.
There is also Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation - I have not read that either, but Fowler-approved books are generally excellent. There's also an older book in the series on Continuous Integration.
If TeamCity is working for you, I'd suggest studying testing first. One of the major values in continuous integration is automated test-running. I can recommend a book on that: The Art of Unit Testing with Examples in .NET.
My personal opinion is that MSBuild scripts are best left to Visual Studio. If having TeamCity run solutions and NUnit/xUnit tests proves insufficient, you might take a look at NAnt. While it is XML-based, I find it easier to understand than MSBuild.