Aspire should get removed from the VMR

[ViktorHofer]

With dotnet/aspire@9f212d8#diff-366b25472963c6b33188d84139f6c8997298c5adc857a2624ab0d26a2d87baf0L10, aspire doesn't produce the workload manifest or any other artifact anymore inside the VMR.

We should be able to remove it from the VMR.

cc @joperezr

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[MichaelSimons]

The aspire workload still getting bundled by the SDK. Note the reference is an out of support 8.n version rather than 9.0. There was a thread with the aspire folks on this. IIRC there wasn't a decision on when they would remove this. @joperezr has there been any decision on this?

SDK workload reference: https://github.com/dotnet/sdk/blob/main/src/Installer/redist-installer/targets/BundledManifests.targets#L19

[joperezr]

Not yet, but if I had to guess, I'd assume this would be done for .net 10.

[ViktorHofer]

@joperezr @danmoseley do you have an update on when the Aspire workload will get removed from the SDK? Asking as this is blocking #4359 (see dotnet/sdk#47254 for more details).

[joperezr]

Same answer as Nov, my guess would be .NET 10. At some point later this year Aspire is planning to ship Aspire 10.0 previews, and I think that this will be the time to take a look at this.