You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm about to start working on a Aspire component to host an emulator of a service that my team is offering to other teams.
The general idea is to have a aspnetcore project whose behavior can be customized via environment variables, package it as a container using the SDK and publish a hosting package built around on the ContainerResource.
I wonder if it's possible to have a single app host that I can use to test both the emulator and the Aspire component.
Am I being too ambitious?
Should I just have two app hosts? One for developing/testing the service and one for developing/testing/showcasing the component?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm about to start working on a Aspire component to host an emulator of a service that my team is offering to other teams.
The general idea is to have a aspnetcore project whose behavior can be customized via environment variables, package it as a container using the SDK and publish a hosting package built around on the ContainerResource.
I wonder if it's possible to have a single app host that I can use to test both the emulator and the Aspire component.
Am I being too ambitious?
Should I just have two app hosts? One for developing/testing the service and one for developing/testing/showcasing the component?
Beta Was this translation helpful? Give feedback.
All reactions