ILSpy

9731 Commits

54 Branches

94 Tags

91 MiB

Tree: 2e9d137e30

Commit Graph

Author	SHA1	Message	Date
Siegfried Pammer	71ac2b9ca9	Fix #3154 : accept single-file bundles as ilspycmd input Every mode loaded the input file with its own `new PEFile(fileName)` call, so a bundle - which the UI opens fine, because LoadedAssembly goes through the file loader registry - failed identically in all of them. The five call sites now share one load helper that runs the same registry, which also makes archives work and keeps one detection point for both front ends. Which assembly inside a bundle is meant is not something to guess, so a package without --bundle-entry lists its managed entries and exits non-zero. The entry point is only annotated in that listing: the manifest has no marker for it, so it is derived the way the host does it, from the runtime-config entry's name, and stays unannotated where that does not resolve. Assisted-by: Claude:claude-opus-5:Claude Code	2 weeks ago
Siegfried Pammer	199b7bf151	Add --dump-table metadata dump mode to ilspycmd The GUI has the metadata-tables view; the CLI had nothing, so checking e.g. which MethodSemantics rows reference a Property row required a hand-written System.Reflection.Metadata script. --dump-table <name> prints every row of a table (RID, token, resolved names, heap offsets, coded indexes) as an aligned text table, or as JSON with --json, for the same 39 Cor tables the GUI shows. Row enumeration for tables without public SRM row access lives in MetadataExtensions next to the existing GetMethodSemantics helper, so the GUI's raw-reading table nodes can be folded onto the shared readers later. Every table's columns are spelled out explicitly in ECMA-335 declaration order: reflecting over the SRM row structs would tie the output (and its column order) to runtime internals, and deterministic output is the point of the feature. JSON uses System.Text.Json from the shared framework, so no new package reference is needed. Assisted-by: Claude:claude-fable-5:Claude Code	2 months ago

Author

SHA1

Message

Date

Siegfried Pammer

71ac2b9ca9

Fix #3154 : accept single-file bundles as ilspycmd input

Every mode loaded the input file with its own `new PEFile(fileName)` call, so a
bundle - which the UI opens fine, because LoadedAssembly goes through the file
loader registry - failed identically in all of them. The five call sites now
share one load helper that runs the same registry, which also makes archives
work and keeps one detection point for both front ends.

Which assembly inside a bundle is meant is not something to guess, so a package
without --bundle-entry lists its managed entries and exits non-zero. The entry
point is only annotated in that listing: the manifest has no marker for it, so
it is derived the way the host does it, from the runtime-config entry's name,
and stays unannotated where that does not resolve.

Assisted-by: Claude:claude-opus-5:Claude Code

2 weeks ago

Siegfried Pammer

199b7bf151

Add --dump-table metadata dump mode to ilspycmd

The GUI has the metadata-tables view; the CLI had nothing, so checking
e.g. which MethodSemantics rows reference a Property row required a
hand-written System.Reflection.Metadata script. --dump-table <name>
prints every row of a table (RID, token, resolved names, heap offsets,
coded indexes) as an aligned text table, or as JSON with --json, for
the same 39 Cor tables the GUI shows.

Row enumeration for tables without public SRM row access lives in
MetadataExtensions next to the existing GetMethodSemantics helper, so
the GUI's raw-reading table nodes can be folded onto the shared
readers later. Every table's columns are spelled out explicitly in
ECMA-335 declaration order: reflecting over the SRM row structs would
tie the output (and its column order) to runtime internals, and
deterministic output is the point of the feature. JSON uses
System.Text.Json from the shared framework, so no new package
reference is needed.

Assisted-by: Claude:claude-fable-5:Claude Code

2 months ago

2 Commits (2e9d137e30feda52bc7247ade2b2b5bdeea14bec)