Convert .sln to .slnx format #314
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Migrates all solution files from legacy
.slnto XML-based.slnxformat usingdotnet sln migrate. Requires .NET SDK 9.0.306+ for tooling support.Changes:
global.jsonSDK version from 8.0.100 to 9.0.306MiniScaffold.slnand template files inContent/{Library,Console}/build/build.fsand template build files) to reference.slnx.slnfilesResult: 154 fewer lines across solution files (-73%), cleaner diffs, fewer merge conflicts.
Types of changes
Checklist
Further comments
Integration tests confirm both library and console templates generate correctly with
.slnxfiles (28/28 tests passed). The XML format is significantly more readable than the legacy text-based format and is the recommended approach per Microsoft's .NET 9 announcement.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.