Claus has written a nice piece on how you can use Roslyn for analyzing your code quality (static code analysis) and run it like any other automated test. Pretty awesome.

However skilled you are as a technician, without the appropriate tools you would still be a dud. Just like a craftsman knows his/her tools, a software professional also has to know the tools that are apt for the job.

Step by step how to integrate FxCop with Visual Studio.

Taking a look at how to add in the ability to run the fxCop static analysis tool to your build script. Having this ability can allow you to keep very close tabs on your code at any time.

Jason Kresowaty designed this web site to address the shortage of documentation on the FxCop 1.36 API. Some of the highlights include the following: - A brief tutorial of FxCop - A listing of what kinds of customizations are possible with FxCop - An overview of the introspection API - ...

This article gives those of us using VS 2005 Professional a few different options for integrating FxCop into the IDE.

In this post I'm going to show a little example of a FxCop rule created with F#.

A summary on creating, deploying and debugging fxcop rules.

Code Analysis perfomance warnings conflict with avoiding premature optimisation.

First in a series of blogs describing my experiences using TFS to improve development practices in our workplace.

Tool : FxCop - Managed Code Analysis