Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Samples should use Aspire where relevant #344

Open
4 tasks
TimHess opened this issue Oct 31, 2024 · 1 comment
Open
4 tasks

Samples should use Aspire where relevant #344

TimHess opened this issue Oct 31, 2024 · 1 comment

Comments

@TimHess
Copy link
Member

TimHess commented Oct 31, 2024

Does a sample use multiple applications and/or backing services? Then it should probably use Aspire.

Anticipating little difficulty (excluding the obvious expected framework changes to merging our service discovery features with new APIs introduced alongside Aspire) in this effort, I think we might be able to get away with a single tracking issue - I'm open to any team member editing this issue to add samples or splitting out into separate issues if my hopes are too naive or the effort gets too messy.

  • Discovery
  • Freddy's BBQ
  • Music Store
  • Management
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants