aspire: [WebToolsE2E][Aspire] After updating .NET SDK to newer band, the Aspire workload does not appear to be installed anymore

REPRO STEPS

  1. Clean machine: Win11 x64 23h2 ENU

  2. Install latest released .NET SDK 8.0.101

  3. Install .NET Aspire workload 8.0 Preview 2

    • Open Command Prompt
    • Run dotnet workload update
    • Run dotnet workload install aspire
    • Result: If you run dotnet --info, you can see that the Aspire workload is installed properly
    • image
  4. Install latest released .NET SDK 8.0.200

  5. Check status of Aspire workload

ACTUAL If you run dotnet workload list, the Aspire workload does not show up anymore

image

image

Workaround: Re-run dotnet workload update and dotnet workload install aspire to re-install the aspire workload

EXPECTED The Aspire workload should continue to show up as installed

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 15 (9 by maintainers)

Most upvoted comments

@v-elenafeng, for the repro steps that you described, I believe this is currently by design. See Marc’s earlier comments here. If you have questions, we can chat more during our next sync meeting.

Reproes with the following config:

  • Clean machine
  • Install SDK 8.0.200
  • Install Aspire 8.0 P4 (latest released)
    • Using CLI, run dotnet workload update and dotnet workload install aspire
  • Install SDK 8.0.300-preview (latest prerelease build)
  • Check if Aspire workload is installed
    • Using CLI, run dotnet workload list

This is a different issue and a bit of a tougher one. We’ve talked about whether new bands should recognize workloads installed by prior bands. They are meant to be completely new SDKs (that we don’t upgrade customers by default through MU but do for VS) but customers could be frustrated on upgrade. I’m trying to remember if our new first run experience includes --from-previous-sdks @MiYanni

CC @dsplaisted @baronfel