-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dotnet run needs a way to pass through arguments starting with - or -- to the executable #5097
Comments
@anurse is this in your backyard, so to speak? :) I think this is a reasonable ask, given the fact that |
This is a System.CommandLine issue I believe. /cc @livarcocc @piotrpMSFT |
Yes. Today, we does not have a "remaing args" option to pass along. We are looking into it. |
This seems like an important ask for many reasons. For example,
@blackdwarf with the shared runtime changes, "quick testing" no longer begins to cover all of the @livarcocc "remaining arguments" won't cut it as shown in the above examples. Of course /cc @davidfowl |
Hmm, maybe this issue is [now] specific to |
I arrived at this issue due to looking for something like the Could I suggest that either the issue title is changed, or a new issue is raised specifically about dotnet test? Basically, I'd be entirely in favour of supporting |
+1 "dotnet test" without passing through arguments cripples those of us wishing to port test frameworks to .NET Core. |
I believe that for |
I'm not sure if the issue truly fixed. If I have a CommandLineApplication and I type: It seems we would need a way for dotnet run to know that there is a help command specific for the app, but then how would we ever get to the help command for dotnet run? Also a sidenote the default shows But I think commands come before options? |
@dotnetshadow you need to use the |
@blackdwarf ahhh thank you that's the thing I missed |
Thnaks, but is this meant to work when launching from VS2017 using IISExpress
But However does work from command line with
|
@davidfowl I'm not sure I'm having a similar issue. If I should open a new issue, I'll do that, let me know. I have a custom CLI tool that I want to relay command line arguments to. Literally, something like this I have serious doubts about this over something like this, At its core, I think possibly I need to see better documentation how to pass command line arguments to my CLI tool. |
@davidfowl I think I've run into what I think is most likely a naming conflict with an already existing nuget |
@mwpowellhtx Since this is a 3 year old, closed, unrelated issue, you'll probably get more eyes and feedback by opening a new issue. |
@plioi I did actually, thanks... |
I have an executable that supports a
--foo
argument. However, runningdotnet run --foo
does not work since the run command attempts to parse it (invalid option --foo
). We need a way to pass through any arguments that aren't consumed by the run command to the executable being launched. This might also apply to thedotnet test
command.The text was updated successfully, but these errors were encountered: