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

This entry was posted on Monday, June 11th, 2007 at 9:29 pm and is filed under /Paul, .NET, Inspection. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.