-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aspire should get removed from the VMR #4735
Comments
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. |
1 similar comment
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. |
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 |
Not yet, but if I had to guess, I'd assume this would be done for .net 10. |
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
The text was updated successfully, but these errors were encountered: