There are 3 different builds for my addins, depending on the kind of depencies they require. *This is list depicts the features of the next drop 4.1.85.2*. All projects can be found on projectdistributor.net.

Each flavor is mutually exclusive! Pick your flavor depending on the dependencies and features that your are looking for!

Dependencies:

• Common requirements:
  • Reflector 4.1.85.0 (or higher)
  • .Net 2.0 Redist

• Reflector.CodeMetrics:
  • Nothing else
• Reflector.Graph:
  • Dependency on NGraphviz (unmanaged assembly)
  • SVG viewer
• Reflector.Framework:
  • Dependency on NGraphviz (unmanaged assembly)
  • SVG viewer

Features:

• Reflector.CodeMetrics
  • CodeMetrics
  • Coverage datagrid
• Reflector.Graph
  • Assembly Graph
  • IL graph (not bullet proof)
  • Statement Graph (not bullet proof)
  • Class diagram (alpha)
  • Method invocation graph (alpha)
  • Typed Dataset (alpha)
• Reflector.Framework
  • All the addins from Reflector.CodeMetrics + Reflector.Graph
  • XmlSerializer viewer (see your object as if it was "XmlSerialized") *locks the assembly*
  • Control viewer (see your winforms control) *locks the assembly*
  • PropertyGrid viewer (see your object as if it was in a PropertyGrid control) *locks the assembly*
  • COM loader (compiles assembly for COM type libraries)  *New*
  • Reflector.Emit language
  • Type TreeMap (supports coverage)
  • IronPython console

Ever wondered what would it take to generate your code on the fly using Reflector.Emit....
The meaning of the following screenshot is left as a quiz...

I've update Reflector.Framework, Reflector.CodeMetrics and Reflector.Graph against the latest version of Reflector.

• They all require .Net 2.0
• Compiled against Reflector 4.1.85.0
• Reflector.Framework requires IronPython assemblies!!!!

It's alive!

A while ago I hooked up Haibo's ILReader to make a rustic Debugger Visualizer for DynamicMethod (Lightweight Code Generation). Haibo did the hard work and made it very interresting tool for debugging those strange .net citizens.

I'm a big fan of custom debugger visualizers. Not only they are very useful but they also very well documented and easily testable! There are already many implementations of those for datasets, xml, etc... but usually it worth investing a little time to build your own customized visualizers.

For example, if your data organized as a tree, you might be continuously drilling down this tree. You could consider a visializer that would render the tree to a certain depth. This will save you a *lot* of "expand node" time.