How can I inject or get access to the async cancellation token before executing a command?

[ptr727]

My console app already has termination handlers for ctrlc/break etc., I configure the environment before calling any command handlers, and I use a my cancellation token in async methods.
I am converting some commands to be async when invoked from the CLI, and I get a cancellation token passed in along with the parse arguments.

Per the docs it looks like CLI configs its own ctrlc handler, and connects the async cancellation token to be signaled.

This duplicates logic my app already manages, how can I e.g. prevent duplicate termination handling being created, pass in my own cancellation token to the CLI logic, reuse the CLI logic cancellation token, etc.?

[richardcox13]

I wanted to disable System.CommandLine's handling of ctrl-c... and after hunting through the code wrote this:

var parse = Cli.RootCommand.Parse(args);
parse.InvocationConfiguration.EnableDefaultExceptionHandler = false;
// Disable ^c (etc.) handling
parse.InvocationConfiguration.ProcessTerminationTimeout = null;
var canTok = SetupInterrupt();

return await parse.InvokeAsync(cancellationToken: canTok);

[ptr727]

Thank you, I was following a similar trail, and it looked like the logic could be controlled with ProcessTerminationTimeout, I'll try it out.

[ptr727]

What is the difference / correctness of setting e.g. ParseResult.InvocationConfiguration.EnableDefaultExceptionHandler after calling parse directly on ParseResult, vs. calling ParseResult.InvokeAsync(InvocationConfiguration) and passing in a configured InvocationConfiguration?

[ptr727]

I looked at the code, no difference, when passing it in it replaces the instance with the passed value.