The current implementation of dotnet CLI mixes definition of CLI Commands with their implementation (SetAction).

Consequently, code that parses CLI transitively depends on the whole SDK (NuGet, Template Engine, VS Test, etc.).

E.g. dotnet-watch is pulling in a lot of dependencies that it shouldn't. The main reason is that we need to know all existing dotnet commands in order to parse dotnet-watch command line correctly and forward options as needed.

This is also problematic for AOT. We want to be able to do all the parsing inside the AOT 'bubble' and decide on a per-command basis where to call.

Related: #51623

TODO:

• tool and workload commands (should be straightforward to convert to the new pattern): Separate command parsing from action binding in Tool and Workload subcommands #52139
• new command - complex dependency on template engine: Template Engine CLI commands: separate definitions from implementations #51747
• nuget commands: Add nuget why and nuget package command definitions #52661
• test command - Separate 'test' command definitions from implementations #51781
• Move all command definitions to a separate library.
  • [template engine cli] Remove dependency on filter definitions from command definitions #52124
  • Completion #52137