ILSpy

9726 Commits

54 Branches

94 Tags

91 MiB

Tree: 4e2f28109e

Commit Graph

Author	SHA1	Message	Date
Siegfried Pammer	16737cc582	Convert BAML to XAML when exporting a project from the command line A WPF assembly keeps its windows and pages as BAML, so a project exported without converting them back is missing the parts that make it a WPF application - and the reader has no XAML to look at either. The CLI could do the conversion since --decompile-baml was added, but only if asked, which meant that everything the project exporter learned about WPF (Page and ApplicationDefinition items, resources, generated members removed from the code-behind) was invisible to anyone following issue #2253 from the command line. The flag is kept and ignored: it is documented and scripted against, and asking for what is now the default has to keep working. The test fixture is a real .g.resources container rather than a directly embedded .baml stream, because only entries inside a container reach WriteResourceToFile - a standalone .baml is copied out untouched, which is worth its own look. Assisted-by: Claude:claude-opus-5:Claude Code	2 weeks ago
Siegfried Pammer	74bc61b70f	ilspycmd: add --member for single-member decompilation Decompiling one method or property previously required decompiling its whole type and searching the output, which is wasteful for scripted and agent-driven use against large assemblies. The new -m\|--member option accepts an XML documentation id string (the syntax of compiler-generated documentation files and of the UI's --navigateto option) or a metadata token in 0x06000005 form, resolves it against the main module (with a bounds check for tokens and distinct error messages for malformed ids, unknown members, and members of other modules), and prints just that member through the engine's single-member decompilation path. The tests seed a new ICSharpCode.ILSpyCmd.Tests project (part of the XPlat and Desktop solution filters and of the per-project CI test steps), driving the real Main in-process via InternalsVisibleTo, so future ilspycmd features have a dedicated home for CLI tests. Assisted-by: Claude:claude-fable-5:Claude Code	2 months ago

Author

SHA1

Message

Date

Siegfried Pammer

16737cc582

Convert BAML to XAML when exporting a project from the command line

A WPF assembly keeps its windows and pages as BAML, so a project exported
without converting them back is missing the parts that make it a WPF
application - and the reader has no XAML to look at either. The CLI could
do the conversion since --decompile-baml was added, but only if asked,
which meant that everything the project exporter learned about WPF (Page
and ApplicationDefinition items, resources, generated members removed
from the code-behind) was invisible to anyone following issue #2253 from
the command line.

The flag is kept and ignored: it is documented and scripted against, and
asking for what is now the default has to keep working.

The test fixture is a real .g.resources container rather than a directly
embedded .baml stream, because only entries inside a container reach
WriteResourceToFile - a standalone .baml is copied out untouched, which
is worth its own look.

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

2 weeks ago

Siegfried Pammer

74bc61b70f

ilspycmd: add --member for single-member decompilation

Decompiling one method or property previously required decompiling its
whole type and searching the output, which is wasteful for scripted and
agent-driven use against large assemblies. The new -m|--member option
accepts an XML documentation id string (the syntax of compiler-generated
documentation files and of the UI's --navigateto option) or a metadata
token in 0x06000005 form, resolves it against the main module (with a
bounds check for tokens and distinct error messages for malformed ids,
unknown members, and members of other modules), and prints just that
member through the engine's single-member decompilation path.

The tests seed a new ICSharpCode.ILSpyCmd.Tests project (part of the
XPlat and Desktop solution filters and of the per-project CI test
steps), driving the real Main in-process via InternalsVisibleTo, so
future ilspycmd features have a dedicated home for CLI tests.

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

2 months ago

2 Commits (4e2f28109e0eae18cbbb72cc65eb37fe49e2e983)