Description
Currently I am developing a project using .NET 8 and the new Aspire tool released by yourselves (in preview).
My issue is around the strange and very unhelpful behaviour exhibited by the dotnet workload tool.
When installing workloads, we have the option to disregard signature checks. This allows installation of packages as part of an unsigned preview release. The issue is that, when an install fails due to a missing package (another issue to be raised), workloads are left in an unusable state despite the workload tool claiming to have performed a rollback of actions.
To fix the situation, I would expect to be able to use dotnet workload uninstall [workload] or dotnet workload clean -all to remove the offending packages, and install non-preview versions by specifying the default nuget package source instead of the dev one. Unfortunately, this is not an options as the installed workloads fail a signature check and removal is not allowed to proceed.
This could be remedied by providing a similar flag that enables signature checking to be skipped as on the dotnet workload install command with the --skip-sign-check flag.
Without such an option, I am currently unable to use any of the affected workloads reliably until either the missing package appears in the dev repo, or a change the the behaviour of the dotnet workload tool has been made.