ILSpy

9740 Commits

54 Branches

94 Tags

91 MiB

Tree: d797d4abb4

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

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

1 Commits (d797d4abb4bf8007d565c1db6d38665999bd8f01)