ILSpy

8917 Commits

24 Branches

90 Tags

71 MiB

Tree: aa92f27e09

Commit Graph

Author	SHA1	Message	Date
Siegfried Pammer	aa92f27e09	Decompile a tiny emitted fixture in the project-export/save/compare tests The Export Project/Solution, Save Code and Compare tests decompiled whatever the default assembly list seeds -- System.Linq, CoreLib, the Uri assembly -- so each spent ~10s purely on type count (Solution/CreateSolution/SaveCode/ DecompileAssembly ~10s, CompareView ~4.5s). Add FixtureAssembly, which emits a minimal two-type assembly via PersistedAssemblyBuilder, and point these tests at it. They still exercise the full project/solution writer, save-to-file and compare-tree pipelines, but each now runs well under a second (e.g. Solution_Mode 10.8s -> 0.3s, CreateSolution 10.8s -> 0.2s, ShowIdentical 4.5s -> 0.3s). Assisted-by: Claude:claude-opus-4-8:Claude Code	4 weeks ago
Siegfried Pammer	0588da3533	Export several selected assemblies as a Visual Studio solution The single-assembly project save was already wired, but selecting multiple assemblies and choosing Save Code only ever saved one of them: SolutionWriter had never been ported, so there was no path that emitted a .sln with one decompiled project per assembly. Port SolutionWriter UI-agnostically and route both Save Code surfaces (the context-menu entry and the Ctrl+S command) through a shared SolutionExport helper that recognises a multi-assembly selection, prompts for the .sln path, runs the export behind the tab's cancellable progress UI, and reports the result into the active decompiler tab (matching how the other long-running commands surface their output). Unlike the prior app, the project-export path writes the .csproj to disk itself and only returns a breadcrumb through the text output, so each project's on-disk file is located after decompiling rather than captured from the output stream. Assisted-by: Claude:claude-opus-4-8:Claude Code	4 weeks ago

Author

SHA1

Message

Date

Siegfried Pammer

aa92f27e09

Decompile a tiny emitted fixture in the project-export/save/compare tests

The Export Project/Solution, Save Code and Compare tests decompiled whatever
the default assembly list seeds -- System.Linq, CoreLib, the Uri assembly --
so each spent ~10s purely on type count (Solution/CreateSolution/SaveCode/
DecompileAssembly ~10s, CompareView ~4.5s).

Add FixtureAssembly, which emits a minimal two-type assembly via
PersistedAssemblyBuilder, and point these tests at it. They still exercise the
full project/solution writer, save-to-file and compare-tree pipelines, but
each now runs well under a second (e.g. Solution_Mode 10.8s -> 0.3s,
CreateSolution 10.8s -> 0.2s, ShowIdentical 4.5s -> 0.3s).

Assisted-by: Claude:claude-opus-4-8:Claude Code

4 weeks ago

Siegfried Pammer

0588da3533

Export several selected assemblies as a Visual Studio solution

The single-assembly project save was already wired, but selecting
multiple assemblies and choosing Save Code only ever saved one of
them: SolutionWriter had never been ported, so there was no path that
emitted a .sln with one decompiled project per assembly.

Port SolutionWriter UI-agnostically and route both Save Code surfaces
(the context-menu entry and the Ctrl+S command) through a shared
SolutionExport helper that recognises a multi-assembly selection,
prompts for the .sln path, runs the export behind the tab's cancellable
progress UI, and reports the result into the active decompiler tab
(matching how the other long-running commands surface their output).
Unlike the prior app, the project-export path writes the .csproj to
disk itself and only returns a breadcrumb through the text output, so
each project's on-disk file is located after decompiling rather than
captured from the output stream.

Assisted-by: Claude:claude-opus-4-8:Claude Code

4 weeks ago

2 Commits (aa92f27e09bf517f6291327485548d40526abf4f)