-
Notifications
You must be signed in to change notification settings - Fork 1.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 --help command #4301
Comments
Here are the common usage scenarios that I see:
|
To sidestep needing to implement help on every command we can call man "dotnet-commandname" in scenario 5. This is the way git handles this same scenario. |
This is great, @ahsonkhan ! @brthor , how does your proposal scale out to Windows? @ahsonkhan, what is your implementation intention here? Will this be a small feature? I'd love to be able to get three implementations, one for each CLI lib listed in dotnet/cli#35 as well as https://github.com/docopt/docopt.net. We could then get your thoughts on which was easiest to work with and most linuxy. thoughts? |
@piotrpMSFT For windows we will need a different strategy because we don't have manpages. Going with Git as an example again, they bring up an html page. This could work but we'd need to generate html in addition to nroff from the docs.json. There are tools like "man2html" which go from nroff to html, but they only seem to work on Linux. Having done this research now, I think implementing --help in each command will be less work and potentially easier to maintain. |
@piotrpMSFT I am using the DNX parser. I can try and use the other parsers and see which one was the easiest to use. However, how do I measure ease of use? |
Just wanted to ping this since I just experienced it on Ubuntu, I typed dotnet restor -s https://myget.org/f/dotnet-core (note the missing e) and got a stack trace (Unhandled Exception: System.ComponentModel.Win32Exception: No such file or directory), I feel it would be more helpful to show a message like "invalid command 'restor'" or similar and then display the help text as if --help had been specified. |
Allow our Build.Tasks.dll to load successfully by packaging its dependent assemblies along side of it.
Add .binlog, and archive it
should support both --help and invalid input.
The text was updated successfully, but these errors were encountered: