If arguments are specified on the command line the arguments specified in launch profile are ignored. However, at least one argument must be specified to ignore the launch profile arguments. There is no way to ignore them and pass no arguments to the app.
This is rather a corner case but the ability is needed to implement Aspire spec correctly in dotnet watch.
Proposal
We propose to add --no-launch-profile-arguments option that forces dotnet run to ignore arguments specified in the launch profile.
Alternatively, we could interpret trailing -- that's not followed by any arguments on the command line as explicitly asking to pass 0 arguments to the app.
If arguments are specified on the command line the arguments specified in launch profile are ignored. However, at least one argument must be specified to ignore the launch profile arguments. There is no way to ignore them and pass no arguments to the app.
This is rather a corner case but the ability is needed to implement Aspire spec correctly in dotnet watch.
Proposal
We propose to add
--no-launch-profile-argumentsoption that forces dotnet run to ignore arguments specified in the launch profile.Alternatively, we could interpret trailing
--that's not followed by any arguments on the command line as explicitly asking to pass 0 arguments to the app.