Monday, November 21, 2005

I have updated my Reflector Addins (download available at http://projectdistributor.net/Releases/Release.aspx?releaseId=274 ).

  1. The big change is that I have splitted the addins into many assemblies which let you load more selectively which one you want.
  2. The second change is that most of the addins are now compiled against .Net 1.1. All the 1.1 addins are in the root directory, while the ones requiring 2.0 are in the 2.0 folder (which also contains a config file)!

.net 1.1 addins:

  • Reflector.CodeMetrics.dll (CodeMetrics)
  • Reflector.Rules.dll (Rules)
  • Reflector.ComViewer.dll (COM viewer)
  • Reflector.DesignViewer.dll (PropertyGrid, Control, XmlSerializer)
  • Reflector.TreeMap.dll (Type Tree Map)

.net 2.0 addins:

  • Reflector.Graph.dll (Assembly Graph, IL Graph, Statement Graph)
  • Reflector.CodeGeneration.dll (Code Generators)
  • Reflector.IronPython.dll (IronPython console. Requires IronPython assemblies in path!)
  • Reflector.Languages.dll (Reflection.Emit language)
  • Reflector.Coverage.dll (Coverage visualization)

Enjoy.

posted on Monday, November 21, 2005 11:24:45 AM UTC  #    Comments [3]
Tracked by:
"used laptop" (online) [Trackback]
"monstera deliciosa" (online) [Trackback]
Wednesday, November 23, 2005 10:54:09 PM UTC
Can't load in reflector any add-in. When loading, throw exception System.ArrayTypeMismatchException. Call stack:
> Reflector.Application!_112._3.Add(string identifier, System.Windows.Forms.Control content, string caption) + 0x25 bytes
reflector.framework.dll!Reflector.Framework.PackageBase.loadWindow(System.Reflection.FieldInfo fi = {System.Reflection.RuntimeFieldInfo}) + 0x240 bytes
reflector.framework.dll!Reflector.Framework.PackageBase.LoadWindows() + 0x5f bytes
reflector.framework.dll!Reflector.Framework.PackageBase.Load(System.IServiceProvider serviceProvider = {Reflector.ApplicationManager}) + 0x60 bytes
Reflector.Application!_139._1(System.IServiceProvider ) + 0x99 bytes
Reflector.Application!_142._1(string ) + 0x26d bytes
Reflector.Application!_142.Load(string[] locations) + 0x20 bytes
Reflector.Application!_140._1(System.Object = {Text="&Add..."}, System.EventArgs = {System.EventArgs}) + 0x131 bytes
system.windows.forms.dll!System.Windows.Forms.Control.OnClick(System.EventArgs e) + 0x54 bytes
system.windows.forms.dll!System.Windows.Forms.Button.OnClick(System.EventArgs e) + 0x2b bytes
system.windows.forms.dll!System.Windows.Forms.Button.WndProc(System.Windows.Forms.Message m) + 0x45 bytes
system.windows.forms.dll!ControlNativeWindow.OnMessage(System.Windows.Forms.Message m) + 0xb bytes
system.windows.forms.dll!ControlNativeWindow.WndProc(System.Windows.Forms.Message m) + 0xbc bytes
system.windows.forms.dll!System.Windows.Forms.NativeWindow.Callback(int hWnd, int msg, int wparam, int lparam) + 0x30 bytes
system.windows.forms.dll!System.Windows.Forms.Control.SendMessage(int msg, int wparam, int lparam) + 0x5c bytes
system.windows.forms.dll!System.Windows.Forms.Control.ReflectMessageInternal(int hWnd, System.Windows.Forms.Message m) + 0x2a bytes
system.windows.forms.dll!System.Windows.Forms.Control.WmCommand(System.Windows.Forms.Message m) + 0x5c bytes
system.windows.forms.dll!System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message m) + 0x20b bytes
system.windows.forms.dll!System.Windows.Forms.ScrollableControl.WndProc(System.Windows.Forms.Message m) + 0x36 bytes
system.windows.forms.dll!System.Windows.Forms.ContainerControl.WndProc(System.Windows.Forms.Message m) + 0x17 bytes
system.windows.forms.dll!System.Windows.Forms.Form.WndProc(System.Windows.Forms.Message m) + 0x27f bytes
Reflector.Application!_110.WndProc(System.Windows.Forms.Message msg = {System.Windows.Forms.Message}) + 0x5d bytes
system.windows.forms.dll!ControlNativeWindow.OnMessage(System.Windows.Forms.Message m) + 0xb bytes
system.windows.forms.dll!ControlNativeWindow.WndProc(System.Windows.Forms.Message m) + 0xbc bytes
system.windows.forms.dll!System.Windows.Forms.NativeWindow.Callback(int hWnd, int msg, int wparam, int lparam) + 0x30 bytes
system.windows.forms.dll!System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message m) + 0xd4 bytes
system.windows.forms.dll!System.Windows.Forms.Control.DefWndProc(System.Windows.Forms.Message m) + 0xb bytes
system.windows.forms.dll!System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message m, System.Windows.Forms.MouseButtons button, int clicks) + 0x75 bytes
system.windows.forms.dll!System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message m) + 0x46e bytes
system.windows.forms.dll!System.Windows.Forms.ButtonBase.WndProc(System.Windows.Forms.Message m) + 0x15a bytes
system.windows.forms.dll!System.Windows.Forms.Button.WndProc(System.Windows.Forms.Message m) + 0x5d bytes
system.windows.forms.dll!ControlNativeWindow.OnMessage(System.Windows.Forms.Message m) + 0xb bytes
system.windows.forms.dll!ControlNativeWindow.WndProc(System.Windows.Forms.Message m) + 0xbc bytes
system.windows.forms.dll!System.Windows.Forms.NativeWindow.Callback(int hWnd, int msg, int wparam, int lparam) + 0x30 bytes
system.windows.forms.dll!System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods+IMsoComponentManager.FPushMessageLoop(int dwComponentID, int reason, int pvLoopData) + 0x325 bytes
system.windows.forms.dll!ThreadContext.RunMessageLoop(int reason, System.Windows.Forms.ApplicationContext context) + 0x160 bytes
system.windows.forms.dll!System.Windows.Forms.Application.RunDialog(System.Windows.Forms.Form form) + 0x34 bytes
system.windows.forms.dll!System.Windows.Forms.Form.ShowDialog(System.Windows.Forms.IWin32Window owner) + 0x44f bytes
system.windows.forms.dll!System.Windows.Forms.Form.ShowDialog() + 0x8 bytes
Reflector.Application!Reflector.ApplicationManager._19() + 0x64 bytes
Reflector.Application!Reflector.ApplicationManager.Execute(string commandName = "Application.AddIns") + 0x371 bytes
Reflector.Application!_152.Execute(string commandName = "Application.AddIns") + 0x99 bytes
Reflector.Application!Reflector.ApplicationManager._7(System.Object = {_149._9}, System.EventArgs = {System.EventArgs}) + 0xa1 bytes
Reflector.Application!_149._8.OnClick(System.EventArgs e = {System.EventArgs}) + 0x22 bytes
Reflector.Application!_149._8.PerformClick() + 0x29 bytes
Reflector.Application!_149._12._1.OnClick(System.EventArgs e = {System.EventArgs}) + 0x3b bytes
system.windows.forms.dll!MenuItemData.Execute() + 0x19 bytes
system.windows.forms.dll!System.Windows.Forms.Command.Invoke() + 0x3b bytes
system.windows.forms.dll!System.Windows.Forms.Control.WmCommand(System.Windows.Forms.Message m) + 0x47 bytes
system.windows.forms.dll!System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message m) + 0x20b bytes
Reflector.Application!_149._3.WndProc(System.Windows.Forms.Message message) + 0x23 bytes
system.windows.forms.dll!ControlNativeWindow.OnMessage(System.Windows.Forms.Message m) + 0xb bytes
system.windows.forms.dll!ControlNativeWindow.WndProc(System.Windows.Forms.Message m) + 0xbc bytes
system.windows.forms.dll!System.Windows.Forms.NativeWindow.Callback(int hWnd, int msg, int wparam, int lparam) + 0x30 bytes
system.windows.forms.dll!System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods+IMsoComponentManager.FPushMessageLoop(int dwComponentID, int reason, int pvLoopData) + 0x325 bytes
system.windows.forms.dll!ThreadContext.RunMessageLoop(int reason, System.Windows.Forms.ApplicationContext context) + 0x160 bytes
system.windows.forms.dll!System.Windows.Forms.Application.Run(System.Windows.Forms.Form mainForm) + 0x34 bytes
Reflector.Application!Reflector.ApplicationManager.Run() + 0x1b bytes
Reflector.exe!Reflector.Application.Run() + 0x36 bytes
Reflector.exe!Reflector.Application._1() + 0x45 bytes
Nikoly Kozemiakin
Saturday, December 17, 2005 1:32:16 PM UTC
Hi Peli,
What's the status on your Graph Library? Is there some place we can get the latest bits and documentation?
Keep up the great work.
Wednesday, December 28, 2005 7:42:41 PM UTC
Great work on these add-ins! I have one request for the Graph add-in, though. I often have the problem that DLLs have references to old (non-existing) versions of other DLLs, while yet other DLLs depend on the correct versions. In the case that a DLL has a reference to another DLL which isn't in the .NET Reflector list, could we have an option to show those dependencies, perhaps in a different color? They would of course be dead ends (since the dependencies of those DLLs weren't loaded in), but it would really help if I see two references to a DLL named "A", but with two different versions...
Ryan Adler
Comments are closed.