dotnet / aspire

Tools, templates, and packages to accelerate building observable, production-ready apps
https://learn.microsoft.com/dotnet/aspire
MIT License
3.93k stars 480 forks source link

[WebToolsE2E][Aspire][Unstable] Deploying 9.0 aspire project, the information in Console log shows "You must install or update .NET to run this application." #6522

Closed vmykagapuz closed 3 weeks ago

vmykagapuz commented 4 weeks ago

INSTALL STEPS

  1. Clean machine: Win11 x64 23h2 ENU
  2. Install SDK 9.0 GA
  3. Install Aspire 9.0 GA
  4. Install VS or VSCode

REPRO STEPS

  1. Open Command Prompt, run the following code to create an aspire starter app dotnet new aspire-starter -o aspire1
  2. Deploy the project in CLI using the following commands:
    azd init
    azd up
  3. Click the link of aspire dashboard
  4. Navigate to Console logs and select any Resources

NOTE

  1. This issue is unstable when deploying 9.0 aspire project.

ACTUAL The State of the project is on 'Pending' and the information shown in Console log of the Resources is different from the usual log infromation. Image Image

EXPECTED The State of the project must show 'Running' and the information shown should be the same with the image below. Image

joperezr commented 4 weeks ago

This is expected as there are no base images that have the GA runtime installed. Can we validate that net8 publishing works as we would expect that scenario to be testable.

vmykagapuz commented 4 weeks ago

@joperezr This issue is unstable it sometimes shows up and sometimes its not. Its also reproduce when deploying with .net8 project.

davidfowl commented 4 weeks ago

This should not happen when released versions. If you are using builds that aren’t yet public then it can happen. It shouldn’t be unstable.

vmykagapuz commented 3 weeks ago

@joperezr This issue is unstable it sometimes shows up and sometimes its not. Its also reproduce when deploying with .net8 project.

For todays validation, I verified that this issue is not reproduce in .NET8 project.

joperezr commented 3 weeks ago

Thanks for confirming. I'm closing this for now. Please feel free to reopen if we see it again.

vmykagapuz commented 1 week ago

This issue is not reproduced in latest-released of VS 17.12