Tutorial on writing your own Code Analysis rule

» Daily Bits - January 19, 2008 (Early Edition) Alvin Ashcraft’s Daily Geek Bits: Daily links plus random ramblings about development, gadgets and raising rugrats.

Sat, 19 Jan 2008 05:15:31 GMT

PingBack from http://www.alvinashcraft.com/2008/01/18/daily-bits-january-19-2008-early-edition/

Static Analysis Rules - Sooner rather than later

Rory Primrose — Wed, 27 Feb 2008 16:42:37 GMT

I posted the other day that I wanted to create some static analysis rules for Visual Studio . I have

FxCop benchmarking

Greg — Wed, 05 Mar 2008 22:10:29 GMT

Has anyone compared FxCop to what static analysis tools available for embedded systems in C++? Those tools are 20+ years old and find an amazing amount of poor code and/or errors. I'd like to se e MS invest heavily in static code analysis tools because it can only a) benefit MS to produce much better code and b) make MS development tools much much better.

FxCop et Code Analysis : écrire ses propres règles

CoqBlog — Sun, 22 Jun 2008 19:10:58 GMT

Voici une documentation qui devrait faire plaisir à ceux qui veulent écrire des règles pour FxCop ou