[release/10.0.1xx-preview6] Prefer CLI commands to loose files #49487
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.
Backport of #49485 to release/10.0.1xx-preview6
Customer Impact
The work to add support for running single-file apps from a direct
dotnet
invocation (dotnet app.cs
) introduces a regression in the way built-in commands are executed. A file that matches the detection criteria for single-file apps that has the same name as one of our built-in commands would be prioritized over the built-in command.Regression
No, this was introduced in p6 and is being fixed in p6, so no users would have encountered this behavior yet.
Testing
Manual testing: what this shows is that while we can run a single-file app with a name matching one of our built-in commands, we can no longer implicitly run it -
dotnet run dnx
works, butdotnet dnx
runs ourdnx
command as expected.Risk
Low, this change is very scoped and only impacts the single-file-run-from-
dotnet
use case.