Improve acquisition for SDK and runtimes

[marcpopMSFT]

• Non-admin install improvements Users can more easily acquire the SDK and runtimes on CI machines and other non-admin installs #14959
• Determine if you have updates available for all admin installed runtime/sdk SDK users can find out if their SDK/runtimes have updates available #14958
• Determine if there are updates for your currently running sdk and runtimes in non-admin locations
• Acquire SDK and runtime from an alternate store Users can acquire the SDK and runtime from an alternate store #14961
• Update your SDK and runtime through a dotnet command SDK users can update their installed runtime and SDKs #14960
• Non-admin uninstall
• Admin and standalone minimal or clean installer

• Support describing .NET runtimes and SDKs as optional workloads #23374
• Create environment manifest of built-in components #23375
• Enable SDK acquisition and management using workload mechanism #23376
• Enable shared framework acquisition and management using workload mechanism #23377
• Support Linux package manager based installations for workloads.

[redradist]

@marcpopMSFT Why this feature Update your SDK and runtime through a dotnet command planned only for .NET 7 ?

[marcpopMSFT]

@redradist It's really a matter of capacity. For .NET6, we are going to focus on the acquisition and update of workloads and then apply the learning from that to updates of the SDK and runtimes themselves.

[richlander]

I'd like to see this feature as NOT an SDK feature, but a runtime one. Our model should be:

• You can update runtimes in prod (with this handy new command).
• You don't need to install the SDK in prod.

[jonnekleijer]

👍 Update your SDK and runtime through a dotnet command