Summary
As discussed in #52717 (comment), we should add component-specific list commands to dotnetup.
Current State
Currently, dotnetup list shows all installed components (SDKs, runtimes, ASP.NET, Windows Desktop).
Proposed Commands
dotnetup sdk list - List only installed SDKs
dotnetup runtime list - List only installed runtimes
- Potentially:
dotnetup aspnetcore list, dotnetup windowsdesktop list
Architecture Considerations
Per @baronfel's feedback:
Having a top-level list is great, but logically it should be similar to calling dotnetup <componenttype> list, and we should be prepared code-architecture-wise to support listing SDKs and Runtimes (and maybe more types of components in the future).
The implementation should:
- Keep
dotnetup list as the top-level command that lists all components
- Add
dotnetup sdk list as equivalent to filtering dotnetup list to SDKs only
- Add
dotnetup runtime list for runtimes only
- Support future component types
Notes
This is intentionally different from dotnet --list-sdks and dotnet --list-runtimes syntax, as those are "among my least favorite parts of our current CLI experience" (@baronfel).
Related
Summary
As discussed in #52717 (comment), we should add component-specific list commands to dotnetup.
Current State
Currently,
dotnetup listshows all installed components (SDKs, runtimes, ASP.NET, Windows Desktop).Proposed Commands
dotnetup sdk list- List only installed SDKsdotnetup runtime list- List only installed runtimesdotnetup aspnetcore list,dotnetup windowsdesktop listArchitecture Considerations
Per @baronfel's feedback:
The implementation should:
dotnetup listas the top-level command that lists all componentsdotnetup sdk listas equivalent to filteringdotnetup listto SDKs onlydotnetup runtime listfor runtimes onlyNotes
This is intentionally different from
dotnet --list-sdksanddotnet --list-runtimessyntax, as those are "among my least favorite parts of our current CLI experience" (@baronfel).Related
dotnetup --info,dotnetup --version,dotnetup list#52717