aspire-configuration

To wire Aspire AppHost configuration without service discovery packages, configure the AppHost to emit explicit environment variables. Bind your application code directly to these variables using IOptions<T> or Configuration to ensure production configuration transparency.

The best way to manage Aspire environment variables for portability is emitting them explicitly from the AppHost. This approach avoids Aspire client packages in application code, ensuring transparent configuration that matches development, testing, and production settings.

To set up Aspire feature toggles matching production, use explicit environment variable configuration wiring. This enables feature toggles for development and testing environments that accurately reflect production settings without relying on service-discovery packages.

Avoiding Aspire client and service-discovery packages in application code enhances maintainability and production configuration transparency. Relying on explicit environment variables instead ensures your application remains portable and decoupled from specific infrastructure packages.

Yes, you can use IOptions<T> to bind Aspire AppHost environment variables in your application. The AppHost emits explicit environment variables, and your application reads them using IOptions<T> or Configuration patterns for transparent wiring.