ILSpy

94 Tags

91 MiB

Tree: 91e9592353

Author	SHA1	Message	Date
Siegfried Pammer	48b8684646	Launch ILSpy from VS Code via dotrush, with a plain fallback dotrush resolves the active target and owns the build task, so the launch and attach configurations go through its commands. Those commands only exist when the extension is installed, so a third configuration builds and launches the apphost directly for setups without it. Assisted-by: Claude:claude-opus-5[1m]:Claude Code	1 month ago
Siegfried Pammer	dd6a9979f4	Load ILSpy.sln via a relative path in the DotRush settings With no configured solution, DotRush only auto-loads when the folder contains exactly one solution file; this repo has several, so it shows a picker and writes the chosen absolute path into .vscode/settings.json, dirtying every fresh clone or worktree. The server resolves configured entries against the workspace folder it is launched in, so a committed relative path works everywhere and stops the write-back. Assisted-by: Claude:claude-fable-5:Claude Code	2 months ago
Siegfried Pammer	bdf7e35e14	Drop the stale net10.0-windows segment from publish-output paths ILSpy targets net10.0, not net10.0-windows; the VS add-in build paths, the installer output dir, the local-dev publish script, and the VS Code launch config still referenced the old net10.0-windows layout. Align them with the actual TFM, matching publish.ps1 and the build workflow. Assisted-by: Claude:claude-opus-4-8:Claude Code	3 months ago
Daniel Grunwald	32cb515f9a	Add VSCode launch config.	1 year ago