Skip to content

Load ILSpy.sln via a relative path in the DotRush settings - #3931

Merged
siegfriedpammer merged 1 commit into
masterfrom
dotrush-relative-solution-path
Jul 29, 2026
Merged

Load ILSpy.sln via a relative path in the DotRush settings#3931
siegfriedpammer merged 1 commit into
masterfrom
dotrush-relative-solution-path

Conversation

@siegfriedpammer

Copy link
Copy Markdown
Member

With no configured solution, DotRush only auto-loads a workspace when the folder contains exactly one solution file. This repo has several (ILSpy.sln, ILSpy.Installer.sln, ILSpy.VSExtensions.slnx, two .slnf filters), so the extension shows a picker and then writes the chosen absolute path back into .vscode/settings.json — dirtying every fresh clone and worktree.

DotRush's language server is launched with the workspace folder as its working directory and resolves dotrush.roslyn.projectOrSolutionFiles entries via Path.GetFullPath, so a committed relative ILSpy.sln works in any checkout location and suppresses both the picker and the write-back. Inert for anyone not using DotRush, and mirrors the existing dotnet.defaultSolution entry.

This PR was authored by an AI agent (Claude Code) operated by @siegfriedpammer.

🤖 Generated with Claude Code

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
@siegfriedpammer
siegfriedpammer merged commit dd6a997 into master Jul 29, 2026
13 checks passed
@siegfriedpammer
siegfriedpammer deleted the dotrush-relative-solution-path branch July 29, 2026 06:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants