Aspire failing in GitHub Codespace

[justinyoo]

Hi, Team.

When the current AppHost is running in GitHub Codespaces (and possibly in devcontainer), I found a few issues:

1. The dashboard page is not automatically opening - (Related to [WebToolsE2E][Aspire] The web page cannot be opened automatically after debugging the aspire project in VS Code. #655 ) Either Blazor app or API app automatically opens a new tab when I run it individually. But, the dashboard doesn't automatically open a new page. Instead I have to manually find the page and open it through the port forwarding tab.

• [CodeSpaces] The launchSettings.json of AppHost doesn't seem to be properly respected #1296

  "applicationUrl": "http://localhost:<random_port_number>",
  "environmentVariables": {
    "DOTNET_DASHBOARD_OTLP_ENDPOINT_URL": "http://localhost:<random_port_number>"
  }

  I initially expected that the applicationUrl attribute will be used to launch the dashboard page, but it uses http://localhost:18888. I'm not sure what these applicationUrl and DOTNET_DASHBOARD_OTLP_ENDPOINT_URL are for.

• [CodeSpaces] Dashboard URIs is looking for a URL that may not work #1297

• [Codespaces] instance is recognised as Production #1298

[timheuer]

Thanks @justinyoo this was a bit of a compound issue, so I logged them individually.

[justinyoo]

@timheuer Thanks for splitting it to individual issues!

[davidfowl]

@timheuer we need to re-test this now that we've moved everything around

[timheuer]

@timheuer we need to re-test this now that we've moved everything around

I'm sure this will still not work due to port forwarding... I don't know enough of the implementation details when we do the project/debugger change areas if it will auto-map the right ports.

[davidfowl]

I want to make sure we do this for v1.

[timheuer]

We need someone more familiar with what's needed to map the ports we all create. Not sure if @kvenkatrajan's team work will automatically get this but with the nature of our proxy ports even within the apphost, I assume we want to map the traefik ones.

[kvenkatrajan]

Since the dashboard in preview 3 is now a "known" executable resource that dcp runs - this should just work. We will have to retest to confirm.