Migrate solution to SLNX format - #934
Merged
Merged
Conversation
- Convert ComputeSharp.sln with the .NET solution migration command - Configure SLNX files to use LF line endings Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 08cf27ea-d94a-4c4e-9049-20f99dd952b9
Sergio0694
marked this pull request as ready for review
September 4, 2026 22:18
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Migrates the root solution from the legacy
.slnformat to.slnxusingdotnet sln ComputeSharp.sln migrate.The migration preserves all 56 projects, solution folders, files, deployment settings, and Debug/Release configurations for x64 and ARM64.
.gitattributesnow applies LF line endings to.slnxfiles.Additional context
Validated all four solution configurations and completed a full Debug/x64 build with Visual Studio MSBuild. The local NuGet proxy workaround is not included in this PR.