Continuous Integration in .NET Review

Average Reviews:

(More customer reviews)Are you looking to buy Continuous Integration in .NET? Here is the right place to find the great deals. we can offer discounts of up to 90% on Continuous Integration in .NET. Check out the link below:

>> Click Here to See Compare Prices and Get the Best Offers

Continuous Integration in .NET ReviewAre you a .NET developer who finds yourself in projects where releasing software is painful and takes forever? Then Continuous Integration in .NET is the book for you. I've been there over and over and thus started researching Continuous Integration tools for .NET about a year ago and found many of which are covered in great detail in the book by Marcin Kawalerowicz and Craig Berntson. The authors are both developers, bloggers, and have vast knowledge and experience with Continuous Integration.
The book is extremely rich when it comes to tools and in under three hundred pages these are some of the tools that are covered; Version control tools like SVN and TFS, unit testing and mocking tools like NUnit and Rhino Mocks, automation tools like NAnt and MSBuild, CI servers like Team City and TFS 2010, UI testing tools, acceptance testing tools, code analysis tools, document generation tools, deployment and delivery tools, and database automation tools. Flavor samples of all the tools you need to automate anything you can think of, and beyond.
In my experience starting with version control, a CI server and Unit testing goes a long way when you're first starting out on the journey towards Continuous Integration. This is also the message [Kawalerowicz and Berntson] sends throughout the book. However, there are quite a bit of content for experienced CI teams as well, e.g. how to take the process even further with automated deployment, database rollouts or how to deal with speed and scalability issues in your build.
In my mind Continuous Integration is so much more than just the tooling and process automation, it is a complete development practice that dictates some of the team's behavior. For instance, to get the rapid and repeated feedback that we strive after all team members need to commit working and tested source code at least daily. I was a bit disappointed that the book didn't cover any of this aspect. In the early chapters the CI concept is redefined by the authors for the scope of the book to exclude the development practice parts.
Continuous Integration in .NET is a very good and well-worked book and I can recommend it to anyone wanting to get started with CI in .NET but don't know how, as well as more experienced CI developers looking to extend and fine tune their process. If you're interested in the development practice side of CI I recommend you read Martin Fowler's article as well as the ground breaking book Continuous Integration: Improving Software Quality and Reducing Risk by Paul Duvall.
Disclosure: Manning Publications contacted me because of my experience and asked for my thoughts on this book. I've received a free copy of the book for this review.Continuous Integration in .NET Overview
Continuous integration is a software engineering process designed to minimize "integration hell." It's a coordinated development approach that blends the best practices in software delivery. For .NET developers, especially, adopting these new approaches and the tools that support them can require rethinking the development process altogether.

Continuous Integration in .NET is a tutorial for developers and team leads that teaches readers how to re-imagine their development strategy by creating a consistent continuous integration process. This book shows how to build on the tools they already know - .NET Framework and Visual Studio - and to use powerful software like MSBuild, Subversion, TFS 2010, Team City, CruiseControl.NET, NUnit, and Selenium.


Want to learn more information about Continuous Integration in .NET?

>> Click Here to See All Customer Reviews & Ratings Now