aspire-configuration

To decouple .NET Aspire AppHost from application configuration, configure the AppHost to emit explicit environment variables. This allows application code to bind directly to IOptions<T> without relying on Aspire client packages or service discovery.

Your .NET Aspire application requires Aspire client packages because the AppHost is not emitting explicit configuration. By wiring AppHost resources to standard environment variables, your app can use standard Configuration bindings and avoid these dependencies.

Yes, you can bind .NET Aspire provisioned resources to standard IOptions<T> without service discovery. The AppHost can be configured to emit explicit configuration via environment variables, allowing standard .NET Configuration binding outside the Aspire environment.

The best way to ensure .NET Aspire configuration transparency for production portability is mapping AppHost resources directly to application configuration keys as environment variables. This decouples application code from Aspire clients, ensuring configuration works outside the Aspire environment.

To map a Postgres resource to a connection string environment variable in .NET Aspire, configure the AppHost to wire the 'postgres' resource to the 'ConnectionStrings__Postgres' configuration key. This exposes the database connection as a standard environment variable.

Configuring .NET Aspire AppHost environment variables does not limit production service discovery; it enhances production parity. By emitting explicit configuration, applications remain portable and transparent outside Aspire, avoiding forced dependencies on Aspire client packages.