Skip to content

Conversation

@gewarren
Copy link
Contributor

@gewarren gewarren commented Mar 4, 2025

Copy link
Member

@BillWagner BillWagner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This LGTM @gewarren

I had one suggestion, and then let's :shipit:

@gewarren gewarren merged commit f1ca307 into dotnet:main Mar 17, 2025
11 checks passed
@gewarren gewarren deleted the more-slnx branch March 17, 2025 16:02
* A single project by specifying the *project.json* file to migrate.
* All of the directories specified in the *global.json* file by passing in a path to the *global.json* file.
* A *solution.sln* file, where it migrates the projects referenced in the solution.
* A *solution.sln(x)* file, where it migrates the projects referenced in the solution.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this change is wrong. The dotnet migrate command was removed in .NET Core 3.0 SDK, and I don't believe the slnx parsing was backported to any older SDKs, so there is no .NET SDK version that can parse slnx in dotnet migrate.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh, good catch, I'll revert. Thanks @KalleOlaviNiemitalo!

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.

4 participants