Robin Munn

Enum names are now GetoptModeV1 and GetoptModeV2 as per discussion with @moh-hassan (see https://github.com/commandlineparser/commandline/pull/684#issuecomment-682600499 and previous comments for background).

@ericnewton76 - Now that there's some motion on the CommandLineParser project again, I'd like to ask you to take a look at this PR. Having `GetOptMode` as a boolean limits...

> Azure DevOps pipelines count any write to stderr as a pipeline error, because why wouldnt it - it's specifically signalling an error! This is a bug in the Azure...

PR #684 (merged into `develop` branch already, though hopefully #690 will also be merged before release 2.9 happens) fixes this by creating a "strict getopt" mode, where `--param -foobar` will...

Until 2.9.0 is released, you can actually make this work by using the `=` syntax: `--parameter=-someValue`. This is a workaround, not the ideal solution, because it means that `--parameter=-someValue` and...

This is essentially a duplicate of #601, BTW.

@jacekard wrote: > @rmunn Hi Robin, could you give an estimate when this MR will be merged? > #690 I can't give you an estimate, sorry. I'd have merged it...

The `EnableDashDash` option has nothing to do with allowing `-Url` to be treated as `--Url`. What it enables is the standard handling of a bare `--` arg (that is, an...

> The first Quick start sample clearly indicates that a boolean parameter can be specified as true or false. > See: https://github.com/commandlineparser/commandline > > But that's just not how it...

Ah, I see. You're misunderstanding the output of that sample program. (Which, to be fair, is badly written and easy to understand). When the sample program outputs "Current Arguments: -v...