The example here looks weird: https://github.com/dotnet/command-line-api/wiki/Your-first-app-with-System.CommandLine.DragonFruit … > dotnet run -- --int-option 123 The value for --int-option is: 0 The value for --bool-option is: False The value for --file-option is: null So the program didn't get the int-option correctly.
-
-
-
Excellent catch!!!!
Kraj razgovora
Novi razgovor -
-
-
Is this based on Microsoft.Extensions.CommandLineUtils or Mono.Options, or is it a completely new thing?
-
It is a completely new thing.
Kraj razgovora
Novi razgovor -
-
-
Serious question, what benefit would I have from this versus using
#PowerShell My first thought is its likely much smaller to ship, would that be a good initial reaction, without having delved into the code base at all? -
Feels orthogonal to PowerShell. It's a command line parser/renderer (rendering is young, but I'm excited about where it is going). If you're writing a console application and need to parse input, this is an easy way to do it while offering a great experience to your users.
- Još 1 odgovor
Novi razgovor -
-
-
Does this make Microsoft.Extensions.CommandLineUtils more deprecated? e.g.https://github.com/aspnet/Extensions/tree/master/src/Shared/src/CommandLineUtils/CommandLine …
-
How do you make something _more_ deprecated?
@natemcmaster still maintains a version of it. System.CommandLine worked to incorporate "lessons" learned in previous parsers. - Još 1 odgovor
Novi razgovor -
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Finally!!!
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.