For Aspire preview.2, some more updates are needed to the setup instructions using VS / CLI with aspire about docs-aspire HOT 8 CLOSED

@joperezr for my comment above for the 'Setup using CLI' part, is there a particular order that you recommend for those commands?

from docs-aspire.

Theoretically the right order is dotnet workload update and then dotnet workload install aspire. Reason is that dotnet workload update will go and update all of the baseline workload manifests you have inside the SDK (a workload manifest is not the workload itself, but simply a "reference" to it which describes which things compose it and what needs to be downloaded if the workload is to be installed), and once those manifests are on their latest version, then you can run dotnet workload install aspire which will then go and download the packs and install them.

That said, I believe in most cases when running dotnet workload install aspire that would also go and internally call update if needed, so it is possible that install alone would be sufficient. That said, this depends on when was the last time that the SDK in the background did a advertising manifest update, so the safest thing is to run update first and then install.

from docs-aspire.

I'm hoping to have a PR for this issue later today or tomorrow. I'm not able to assign myself for some reason.

from docs-aspire.

My PR currently addresses the text issues and the first screenshot. I'll push again when I have preview.2 running.

from docs-aspire.

FWIW, I also created a PR in aspire repo that will add instructions on how to test against the latest version of preview 2.

from docs-aspire.

Thanks @joperezr - I've updated to preview 2 with your scripts, which worked perfectly. All @balachir's issues are now fixed except the last one. Even though Preview 2 is in place, the NuGet package manager still shows 8.0.0-preview.1 versions. I can get it to show 8.0.0-preview.3 by selecting the dotnet8 package source and clearing the search box, but no preview 2 versions anywhere. But this is expected, right? Thanks!

from docs-aspire.

Preview 2 packages will show in nuget.org after we ship it. To see them in the package manager before we release, you just need to add the package source: https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json

from docs-aspire.

Preview 2 packages will show in nuget.org after we ship it. To see them in the package manager before we release, you just need to add the package source: https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json

Thanks @joperezr. I think we'll put up with the old version numbers.

To resolve some conflicts I've closed the original PR and created this new one: #208

Should be ready to merge.

from docs-aspire.