[release/10.0.1xx] Avoid discarding file-like arguments in dotnet file.cs invocations
#52266
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
jjonescz
added
Area-run-file
jjonescz
approved these changes
Dec 22, 2025
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.
Backport of #52110 to release/10.0.1xx
/cc @baronfel @jjonescz
Description
Fixes a bug where
dotnet run file.cs file.csdidn't parse correctly the secondfile.csas an argument for the file-based app (instead it was ignored). Note thatdotnet run file.cs anything-else-than-file.csalready parses correctly, it's just the edge case where the argument matched the file path that was broken.Customer impact
This was reported by a customer as an issue on GitHub.
Regression
No, as far as I know this didn't work since
dotnet file.cssupport was introduced.Risk
Low. A simple change with narrow impact. Unit test coverage.