Closed justinyoo closed 2 weeks ago
Thanks @justinyoo this was a bit of a compound issue, so I logged them individually.
@timheuer Thanks for splitting it to individual issues!
@timheuer we need to re-test this now that we've moved everything around
@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.
I want to make sure we do this for v1.
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.
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.
clarified title (because we could also set up a codespace for this repo)
Pending validation.
@kvenkatrajan I assigned this to you.
Aspire launch debug in C# dev kit is currently working on linux, as of end of last week - we are unblocked on testing.
Summary after testing:
We were able to test the experience of C# dev kit in code spaces with the new version of C# dev kit and here were our early observations :
Moving to backlog. We should decide whether this goes in for 9.0.
I did some experimentation this weekend on how to make the upcoming version of .NET Aspire (9.0) work with GitHub Codespaces. Here is what I did.
The first step is creating a GitHub repo and creating a new .NET Aspire project in it (I used the starter project). Next I opened that container and tweaked the .devcontainer file:
https://github.com/mitchdenny/aspire-withcodespaces/blob/main/.devcontainer/devcontainer.json
Then in the Program.cs
of the AppHost I created this extension method class:
And wired it up to the builder like this:
Then you should just be able to install the C# extensions and F5 the project and it'll start up. The WithCodespaces(...)
extension figures out the right forwarded URLs and replaces them on the dashboard:
@bradygaster this currently blocks the Aspire templates from publication to curated collection, due to invalid devcontainer config. Would love to chat about this.
@anfibiacreativa get the list of things together to smooth out the experience and let me know. also curious if @claudiaregio has seen this and has any ideas.
@mitchdenny I see this is marked as completed, but I just tried creating an Aspire app on Codespaces and it does not launch. Is there a specific configuration/version this works on?
Completed in main, 9.1.0-*. If you want to give it a try https://github.com/dotnet/aspire/blob/main/docs/using-latest-daily.md
Hi, Team.
When the current AppHost is running in GitHub Codespaces (and possibly in devcontainer), I found a few issues:
[x] #1296
I initially expected that the
applicationUrl
attribute will be used to launch the dashboard page, but it useshttp://localhost:18888
. I'm not sure what theseapplicationUrl
andDOTNET_DASHBOARD_OTLP_ENDPOINT_URL
are for.[x] #1297
[x] #1298