dotnet sln remove smart project matching

[edvilme]

Fixes #47111

dotnet solution remove baz

This would find a .csproj file named baz.csproj in the solution, independent of the path to the project. If there is a conflict (aka, multiple baz.csproj files), it would error. Otherwise, it would do the smart thing, find the project defined as foo/bar/baz/baz.csproj and remove it.

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

src/Cli/dotnet/commands/dotnet-sln/remove/Program.cs:80

• The empty catch block may suppress unexpected exceptions that could help diagnose issues. Consider catching a specific exception or logging the caught exception to aid in troubleshooting.

if (project is null && !Path.HasExtension(projectPath)) { try { ... } catch { project = null; } }

[richlander]

This seems like a good idea. I haven't run into this but I can see how annoying the current behavior would be.

[edvilme]

Couple design remarks

• The current behavior when the command doesn't find a project is to print an error message, without failing. To keep consistency, I think that should still be the case here
• The issue mentioned .csproj, but I think it would align more with user expectations if it detected any project extensions

[edvilme]

Re-targeted to main to be released on .net 10 instead