Andrew Savinykh

> As a middleware, UseExceptionHandler applies to all commands, so it satisfies DRY. Sorry, my comment regarding DRY was specifically in response to suggestion of catching exceptions in command handlers....

I disagree. CommandLine is a library, in my opinion a library should not catch exceptions it did not produce. If you change the handler to only catch exception that may...

@jonsequitur, thank you for engaging in this discussion, I really appreciate your time. I feel that we have different ideological priorities, which will not be aligned in this thread. It...

So the solution I ended up with, in additions to the `new CommandLineBuilder(rootCommand).Use` multi-line monstrosity is this: ``` static class CommandHandlerWrapper { public static async Task ExecuteCommandHandler(T options, Func handler)...

@MKlimuszka Could you please link the commit where this is fixed?

I consent to the license changing to MIT

@hansw-nlo as far as I understand, the change in license is because it is not longer sold - I could be wrong. Moreover that would be incompatible with MIT, which...

A statement from those in control of the repo would be nice to explain the community and the contributors what's happening and why.

@Miserlou as mentioned earlier in this thread a workaround would be to wrap your app in a timeout script. There is an example of how you can do it above....

The .Net API gives "A required privilege is not held by the client", when you are an administrator and not running an elevated PowerShell. I'm on Win 10 build 19044....