As of December 1st, the Microsoft Store in Redmond will for the first time start carrying books from publishers other than Microsoft Press. My book, Continuous Integration: Improving Software Quality and Reducing Risk, is one of those books. For the time being, the book will only be available at the physical store, not at the online Microsoft store.

One of my goals from the beginning in writing the book was to provide examples in many different languages/platforms. In the book, we cover C#/NAnt examples, .NET static analysis tools along with Java and Ruby examples. There’s something for everyone. CI, as a practice, is independent of any particular tool. That said, tools greatly support the practice, given the vast array of code inspection, build, and CI servers on the market. So, if you’re a Microsoftie and are curious about CI or are currently using the daily build practice, purchase a copy, or three, for yourself at the Redmond store.

In Chapter 7, Andy covers practices for automated static/dynamic analysis so that you can discover overly complex code, code coverage, or code that doesn’t adhere to your project’s standards early in the lifecycle. He uses plenty of examples for the Java and .NET platforms. Below, is a list of inspection tools for .NET:

• NCover - code coverage
• Clover.NET - commercial code coverage for .NET
• CCMetrics - measure code complexity in .NET
• SourceMonitor - see inside your software source code to find out how much code you have and to identify the relative complexity
• FxCop - A code analysis tool that checks for conformance to the .NET Framework Design Guidelines