ILSpy

9026 Commits

24 Branches

90 Tags

71 MiB

Tree: 8696b691e6

Commit Graph

Author	SHA1	Message	Date
Siegfried Pammer	51aafa0fd9	Move ILSpy UI code back to the ICSharpCode.ILSpy root namespace The Avalonia port had placed the UI app in an ILSpy.* namespace tree, while the csproj RootNamespace and every prior release (through 10.1) use ICSharpCode.ILSpy.*. Restoring the historical namespace reduces the public API diff against release/10.1 for plugin authors and removes the shadowing that forced global:: qualifiers in the test project. The Images class and AccessOverlayIcon enum move back into the root namespace (as in 10.1), since an ICSharpCode.ILSpy.Images namespace would shadow the Images class for all code inside ICSharpCode.ILSpy. Assisted-by: Claude:claude-fable-5:Claude Code	4 weeks ago
Siegfried Pammer	0826bae4a5	Record fast distinct navigations instead of collapsing them NavigationHistory.Record's 0.5s debounce collapsed ANY two selections inside the window -- including two DIFFERENT nodes -- so a navigation whose decompile finished quickly (cheap targets, or a fast machine) never pushed the previous node onto the back stack, silently losing history. Its real purpose is only to swallow the double-fire a single click produces (SelectedItems.CollectionChanged + SelectedItem PropertyChanged, same node) and tree-refresh re-selects, so gate the collapse on the rapid entry being equal to the current one; a distinct node now records normally. The view-state/navigation tests navigate between two cheap namespace nodes (a C# namespace decompiles to just its "// Some.Name.Space" line) instead of decompiling CoreLib types in full -- fast enough for the headless 15s budget on slow CI runners, and a direct regression test for the collapse bug above. Assisted-by: Claude:claude-opus-4-8:Claude Code	4 weeks ago
Siegfried Pammer	96d50e2b5b	Run long operations in their own frozen tab Project/solution export, PDB generation, Create Diagram and Extract Package all ran via RunWithCancellation on the active preview tab -- whose cancellation token tree-node navigation cancels. So selecting any node while one of these ran killed it: you couldn't browse while an export was in progress. Add DockWorkspace.RunInNewTabAsync, which opens a new frozen document tab (its own decompile/cancellation scope, never the navigation target), runs the work there, and shows the report in it. Route the long-running command sites through it. A frozen tab is immune to the selection-driven re-decompile, so navigation can no longer cancel the work -- and the report opens in its own tab instead of replacing the current view. The single-node Save Code path intentionally stays on the active tab (matches the prior version and is quick). Assisted-by: Claude:claude-opus-4-8:Claude Code	4 weeks ago

Author

SHA1

Message

Date

Siegfried Pammer

51aafa0fd9

Move ILSpy UI code back to the ICSharpCode.ILSpy root namespace

The Avalonia port had placed the UI app in an ILSpy.* namespace tree,
while the csproj RootNamespace and every prior release (through 10.1)
use ICSharpCode.ILSpy.*. Restoring the historical namespace reduces the
public API diff against release/10.1 for plugin authors and removes the
shadowing that forced global:: qualifiers in the test project. The
Images class and AccessOverlayIcon enum move back into the root
namespace (as in 10.1), since an ICSharpCode.ILSpy.Images namespace
would shadow the Images class for all code inside ICSharpCode.ILSpy.

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

4 weeks ago

Siegfried Pammer

0826bae4a5

Record fast distinct navigations instead of collapsing them

NavigationHistory.Record's 0.5s debounce collapsed ANY two selections inside the
window -- including two DIFFERENT nodes -- so a navigation whose decompile finished
quickly (cheap targets, or a fast machine) never pushed the previous node onto the
back stack, silently losing history. Its real purpose is only to swallow the
double-fire a single click produces (SelectedItems.CollectionChanged + SelectedItem
PropertyChanged, same node) and tree-refresh re-selects, so gate the collapse on the
rapid entry being equal to the current one; a distinct node now records normally.

The view-state/navigation tests navigate between two cheap namespace nodes (a C#
namespace decompiles to just its "// Some.Name.Space" line) instead of decompiling
CoreLib types in full -- fast enough for the headless 15s budget on slow CI runners,
and a direct regression test for the collapse bug above.

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

4 weeks ago

Siegfried Pammer

96d50e2b5b

Run long operations in their own frozen tab

Project/solution export, PDB generation, Create Diagram and Extract
Package all ran via RunWithCancellation on the active preview tab --
whose cancellation token tree-node navigation cancels. So selecting any
node while one of these ran killed it: you couldn't browse while an
export was in progress.

Add DockWorkspace.RunInNewTabAsync, which opens a new frozen document
tab (its own decompile/cancellation scope, never the navigation target),
runs the work there, and shows the report in it. Route the long-running
command sites through it. A frozen tab is immune to the selection-driven
re-decompile, so navigation can no longer cancel the work -- and the
report opens in its own tab instead of replacing the current view.

The single-node Save Code path intentionally stays on the active tab
(matches the prior version and is quick).

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

4 weeks ago

3 Commits (8696b691e6285e6ab9bbe70e277799a2d9a25e6b)