Is FxCop internals being used in any other products

Hi Michael,
First let me say thanks for all the support your providing on this forum.

In browsing around the different threads it seems like you elude to the fact that the engine that FxCop uses for its analysis is also used in other ways / places / products. Specifically when you say that many of the exposed methods dont do anything because it could be used to parse abstrace syntax trees from source, but FxCop uses it as a binary interpreter of the IL and many of these constructs dont exist in IL.

I also noticed a while back a microsoft research paper titled"Common Compiler Infrastructure". The paper is very rough in details (i think generated from a power point file) but a lot of the code API seems to be very similar to the publicly exposed API in the various FxCop dlls.

Is the FxCop engine part of a larger plan / product? Is it an offshoot from another project?

Dont know if you can say, but I'm curious.
Thanks
John

[1286 byte] By [JohnCMCSD] at [2007-12-17]
# 1
Yes, FxCop currently depends on a portion of the 'common compiler infrastructure' project for its work. 'CCI' is a set of compiler components, one of which is a binary metadata reader. This is the portion that FxCop reuses. CCI also defines the abstract syntax tree representation that's raised from method IL.

Right now, we're looking at creating what we call a 'universal metadata representation'. This is simply a stable abstraction to represent managed (and eventually native) metadata that could potentially be overlaid over any arbitrary library that cracks managed and win32 files. It seems clear that FxCop has matured sufficiently that we need to expose a more focused (and documented) API for custom rules developers. As you've noted, CCI exposes some constructs that look very valuable for rules writers, but which, unfortunately, aren't relevant to binary analysis (rather than source compilation).

MichaelFanning-MS at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Visual Studio Code Analysis and Code Metrics...
# 2
Dough! I never put Microsoft.Cci and Common Compiler Infrastructre together. Thanks for the info and insight into FxCop.
JohnCMCSD at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Visual Studio Code Analysis and Code Metrics...

Visual Studio Team System

Site Classified