pimhwang/ILSpy - ILSpy - git.quantfans.net

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	3 months ago
Siegfried Pammer	91133c1272	Keep the tree selection put when right-clicking a node Right-clicking a tree row to reach its context menu used to move the real selection there first, because ProDataGrid selects the row on press. With the preview document bound to the selection, that meant 'Decompile to new tab' on node B (while viewing A) jumped the preview to B before the command ran, so you ended up with B twice instead of the intended A + B. Middle-click avoided it, but not every mouse has a usable one. Capture the right-clicked row in ContextRequested (which fires even when a previous menu's light-dismiss popup swallows the press) and swallow the right-press so the grid never reselects: the menu now acts on the clicked row as a Thunderbird-style context target while the selection -- and the document -- stay put. The targeted row gets a faint focus-box highlight, cleared when the menu closes (guarded so a stale menu's close can't wipe a newer target). Also adds TestHarness.ClickItem to collapse the repeated Items.OfType<MenuItem>().Single(...).RaiseEvent(...) menu-click dance. Assisted-by: Claude:claude-opus-4-8:Claude Code	3 months ago
Siegfried Pammer	f466b2399b	Add per-step visual breakpoints to the headless UI tests To audit what each UI test actually exercises, every step now snapshots the live window to <TestFixtureName>/<TestName>_<NN>_<ShortDescription>.png: a booted frame (emitted automatically by TestHarness.BootAsync), one after each state-changing action, and one before each assertion. Flip ILSPY_TESTS_VISIBLE=1 to render the filmstrip; it lands under %TEMP%/ilspy-test-captures (overridable via ILSPY_TEST_CAPTURES). The step number and fixture/test name are derived automatically so inserting a breakpoint never renumbers the rest. The identity is recorded up front from the real ITest in an ITestAction hook rather than read live: NUnit's TestContext.CurrentContext does not flow onto async continuations, so a capture after an await would otherwise collide under the ad-hoc context. And when rendering is off the whole call is a true no-op -- not even a dispatcher pump -- so instrumenting a test can never perturb the navigation/tab timing it asserts on. Full headless suite stays green.	3 months ago
Siegfried Pammer	56afcf8abd	Factor repeated headless-test setup into shared helpers Nearly every headless UI test opened with the same four-line prologue (resolve the shared MainWindow, show it, cast its DataContext, wait for the assembly list), then repeated the corelib lookup, the EnsureLazyChildren + Children.OfType<T>().Single() drill, the registry single-by-header lookups, and the open-an-assembly-and-wait dance. The duplication made the intent of each test hard to see and every signature tweak a suite-wide edit. Collapse those into TestHarness (BootAsync, OpenAssemblyAsync, GetCommand, GetEntry) and TreeNavigation extensions (FindCoreLib, GetChild<T>, Expand<T>), then apply them across the suite. Net ~865 lines of boilerplate removed with no change in behaviour; the full headless suite stays green.	3 months ago
Siegfried Pammer	a16d40c5a4	Drive context-menu tests through the live menu builder The Reload/Remove/SearchMSDN/OpenContainingFolder/DecompileInNewView tests used to call `entry.Execute(synthetic TextViewContext)` against a hand-built context. They now select via the assembly-tree model, build the context menu through `BuildContextMenuForCurrentState` (the same call the live `Opening` event makes), and fire the menu item's `Click` routed event — the same handler the user's click invokes. This widens the coverage to the menu-build → click-handler attachment pipeline. Assisted-by: Claude:claude-opus-4-7:Claude Code	3 months ago
Siegfried Pammer	4ad25ae63a	Reload context-menu entry on assembly nodes Mirrors the WPF host's nested ReloadAssembly entry. Same visibility shape as Remove (every selected node must be an AssemblyTreeNode). Execute calls AssemblyList.ReloadAssembly on each selection's path, snapshots the pre-reload tree paths so that after the LoadedAssembly instances are swapped out the model can re-select an equivalent node via FindNodeByPath. The existing SelectedItem -> ShowSelectedNode plumbing then re-decompiles into the active tab. Assisted-by: Claude:claude-opus-4-7:Claude Code	3 months ago