Adding nightly dogfooding devcontainer

[joperezr]

Description

Adds a dogfooding devcontainer that can be used to setup an environment where people can test the latest version of aspire pushed to our nightly feeds. After this one goes in, we can also build one that uses live-built bits.

cc: @mitchdenny

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

Microsoft Reviewers: Open in CodeFlow

[danmoseley]

do we care about any of these
https://github.com/dotnet/runtime/blob/45b75201f3703414ad4fbbc883adf6e378d8f2f9/.devcontainer/devcontainer.json#L27

[danmoseley]

or https://github.com/dotnet/aspnetcore/blob/3ba179ad088127e35a2a3e4ca8bc24bfc099fef2/.devcontainer/devcontainer.json#L31

[danmoseley]

or gh cli https://github.com/dotnet/runtime/blob/45b75201f3703414ad4fbbc883adf6e378d8f2f9/.devcontainer/devcontainer.json#L16

[joperezr]

I think we should consider all of those but for the other devcontainer (the contributing one) which is already checked in (cc: @mitchdenny ) That is because most of those settings relate to working on the repo itself, and that is what our contributing dev container is for. This one that I'm adding here, is instead for having a blank slate that has latest nightly installed in an empty workspace with the right nuget.config defined, so anyone can dogfood aspire's latest build from main. The settings you pointed out may not be applicable for this one.

[danmoseley]

gotcha

[joperezr]

Thanks folks!

[davidfowl]

@joperezr How do I use this?

[joperezr]

@joperezr How do I use this?

In the aspire repo, open the Codespaces -> ... -> New with options...

And then from Dev container configuration -> .NET Aspire - Dogfood (Nightly)

[davidfowl]

Should we put this in the dogfooding instructions.