aspire-configuration

You can expose Aspire AppHost resource outputs as environment variables by configuring explicit mappings in the AppHost, which decouples your application code from Aspire clients and service-discovery concerns. This allows the app to bind config sections directly to IOptions<T>.

Decoupling application code from Aspire clients ensures production parity by representing every external dependency as explicit configuration, allowing the app to run in production without the Aspire runtime while keeping hosting logic isolated inside the AppHost.

Yes, you can bind Aspire environment variables to IOptions<T> by establishing explicit config mappings that convert AppHost resource outputs into clear configuration sections, which the application can then bind to strongly typed options objects.

The best way to achieve production parity with .NET Aspire AppHost is translating resource outputs into explicit environment variables, ensuring all external dependencies like databases and containers can be reproduced in production without requiring the Aspire runtime.

Restricting Aspire client usage to the AppHost does not break service discovery; instead, it enforces safe isolation by pushing service-discovery concerns into explicit environment variable mappings, keeping application projects decoupled from Aspire hosting logic.