Skip to content

Migrate ILSpy.sln to the SLNX solution format - #4274

Merged
siegfriedpammer merged 1 commit into
masterfrom
slnx-migration
Oct 23, 2026
Merged

siegfriedpammer merged 1 commit into
masterfrom
slnx-migration

Conversation

@christophwille

Copy link
Copy Markdown
Member

Replaces ILSpy.sln with ILSpy.slnx, produced by dotnet sln ILSpy.sln migrate. The solution content is unchanged: same projects, same solution folders and items, same platforms. The old per-project configuration mappings all mapped every solution platform to Any CPU, which is the SLNX default for .csproj projects, so they are not carried over. ILSpy.Installer.sln stays in the old format.

Every script, workflow, solution filter and doc that named ILSpy.sln now names ILSpy.slnx. Verified locally: restore.ps1 + build.ps1, a build through ILSpy.Desktop.slnf, dotnet-format whitespace --verify-no-changes ILSpy.slnx, and no packages.lock.json churn.

Action required for existing clones

Every developer with an already checked-out repo must refresh their pre-commit hook from BuildTools/pre-commit (copy it over .git/hooks/pre-commit; a symlinked hook picks the change up automatically). The old hook runs dotnet-format against ILSpy.sln, which no longer exists, so every commit fails until the hook is refreshed.

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

🤖 Generated with Claude Code

Produced by "dotnet sln ILSpy.sln migrate" and renamed to the repo's
casing so the Linux and macOS CI jobs find it. The per-project
configuration mappings of the old file are not carried over because
they all mapped every solution platform to Any CPU, which is the SLNX
default for .csproj projects. ILSpy.Installer.sln stays in the old
format. Every script, workflow, solution filter and doc that named
ILSpy.sln now names ILSpy.slnx.

Assisted-by: Claude:claude-fable-5-1:Claude Code
@siegfriedpammer
siegfriedpammer merged commit c08aab3 into master Oct 23, 2026
20 checks passed
@siegfriedpammer
siegfriedpammer deleted the slnx-migration branch October 23, 2026 06:12
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