Migrate solution from .sln to .slnx format #164
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Remove legacy Slugify.sln file - Add new Slugify.slnx file using dotnet sln migrate - Maintains all existing project references and configurations - GitHub Actions workflows remain compatible with new format
|
On hold until .NET10 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR migrates the solution file from the legacy .sln format to the new .slnx format introduced in recent versions of .NET.
Changes Made
Benefits
Testing
The migration preserves all existing functionality:
The dotnet CLI commands in GitHub Actions automatically detect and use .slnx files, so no workflow changes are required.