pimhwang/ILSpy - ILSpy - git.quantfans.net

Author	SHA1	Message	Date
Christoph Wille	d6bf916398	Fix unreachable-process and selection defects in the process dialog A refused unix socket raises SocketException, which derives from Win32Exception rather than IOException, so it escaped the filter meant to skip one unreachable process and failed the whole concurrent enumeration instead: a machine where any .NET process exits between the port scan and the connect showed an empty list. The classification is now a named predicate covering both transports. Two dialog defects shared a shape - state left behind by a query nobody is waiting for any more. Rebuilding the bound collection on every filter keystroke made the grid drop its selection and write that null back, discarding the assemblies of a process the new filter still matched; and the branch taken when nothing is selected cleared no loading flag, while the query it superseded was no longer allowed to, so the progress bar animated over an empty pane. Relatedly, the two-second command budget expired into a process listed with null metadata, which made a slow machine look like a runtime that answered with nothing; it is longer now, and expiry names the process it gave up on, since the only thing that ever reaches the far end of that budget is a runtime which will never answer. The test gaps are closed the same way: a real dynamic assembly pins the in-memory classification, the managed-only assertion is stated as the property instead of a list of native names to exclude, and the .NET Framework path gets live tests. Those showed that a desktop CLR process mostly reports NGen native images rather than the IL assemblies behind them, which is now recorded as the fidelity gap it is. Assisted-by: Claude:claude-opus-5:Claude Code	2 months ago
Christoph Wille	719e863679	Add "Open from running process" dialog With a modern .NET app the executable in the process list is a native apphost that carries no IL, so the path a user can see is precisely the one a decompiler cannot open - ILSpy itself is an example. Ask the runtime instead: since .NET Core 3.0 every CoreCLR process serves a diagnostics endpoint that names its managed entry assembly and, via an EventPipe rundown, every assembly it has loaded, including ones behind a single-file bundle or with no file at all. The endpoint answers the same way on Windows, Linux and macOS and needs no privileges beyond same-user, which also makes it the only workable route on macOS, where native process introspection is gated by SIP. The protocol and the nettrace container it returns are implemented here rather than taken from Microsoft.Diagnostics.NETCore.Client, so the feature costs no new package reference; the reader is scoped to loader rundown events and steps over everything else by size. The rundown asks for the loader keyword alone: the runtime's default set also collects the JIT and IL-to-native-map rundown, which in a long-running process buries the module list and overruns the session buffer, costing the very events the dialog needs. Windows additionally lists .NET Framework processes, which predate the endpoint and are read from their OS module list instead. Assisted-by: Claude:claude-fable-5:Claude Code	2 months ago
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
Christoph Wille	358ec20dd9	Add Open from NuGet feed dialog for browsing and opening packages Opening a package from a feed previously meant downloading the .nupkg by hand and using File > Open (#2313). The new File menu command searches any public V3 feed (editable package-source list, persisted as an MRU in the ILSpy settings), offers the latest 100 versions in a dropdown, and downloads into the NuGet global packages folder so the cache is shared with every other NuGet consumer on the machine and nothing is fetched twice. The cached .nupkg is then opened exactly like the regular Open command. Feed access sits behind INuGetFeedClient so the headless test suite covers search, paging, version selection, download, cancellation, and error surfacing without touching the network. Assisted-by: Claude:claude-fable-5:Claude Code	3 months ago
Siegfried Pammer	d2df519ba8	Let the native menu derive item enabled-state from CanExecute The menu builder hard-set each NativeMenuItem's IsEnabled from static export metadata (always true), overriding the state that assigning Command would otherwise derive from the command's CanExecute. The inline NativeMenuBar on Windows/Linux re-derives from the command and greys out OS-gated items (e.g. Open from GAC, which is Windows-only), but the macOS native menu reads NativeMenuItem.IsEnabled directly -- so those items stayed enabled there even though invoking them is a no-op. Drop the explicit IsEnabled so every command-backed item follows its CanExecute on all platforms. Assisted-by: Claude:claude-opus-4-8:Claude Code	3 months ago