Jon Sequeira

> I guess the question I really have is: maybe I'm missing something, but what is your resistance to adding a way to do case-insensitive commands and options here? By...

Yes. We wanted to limit the number of overloads. But it should be straightforward to define your own extension methods if you prefer to have the parameters for both injected...

@bording The `InvocationContext` should give you access to everything you need. You can get to the `IConsole` instance using `InvocationContext.Console` and you can get a `CancellationToken` (triggering Ctrl+C [cancellation handling](https://docs.microsoft.com/en-us/dotnet/standard/commandline/handle-termination))...

> Should I use the `Option` instead of `Option` since the the `Option` is `abstract` now Yes. When you declare options and arguments, you'll need to use `Option` and `Argument`....

> Now that options are required to be passed to SetHandler (I like this change), how about allowing us to omit also adding them directly to the command. We've looked...

> So what should I do now if I used one of removed overloads? I was passing 11 of Option into SetHandler. @tomrus88, you can either use a custom `BinderBase`...

@bgever @NickStrupat I hit on more or less the same solution. @FroggieFrog You could use this same pattern to bind your `IConsole` parameter. The rest of your original code should...

> So what "just worked" before, now needs to be done by hand with way more lines of code? @FroggieFrog Here's the implementation I'm using. It might be reasonable to...

> This code looks like it is written by someone who is writing code for the first time. There is so much duplication in it that i am wondering who...

Those of us working on System.CommandLine are also not satisfied yet with this API, which is why there's still a beta tag on it. The changes so far have been...