aspire-configuration

To decouple application configuration from Aspire, enforce explicit mapping from Aspire AppHost resources to application environment variables. This removes direct Aspire client package dependencies, allowing standard configuration binding.

Explicit environment variables for Aspire AppHost resources ensure production parity by making all configuration transparent and settable outside of Aspire. This guarantees applications remain portable without Aspire-specific service discovery mechanisms.

Yes, you can bind configuration to IOptions<T> without direct Aspire client references. The Skill translates Aspire resource outputs into explicit configuration keys, allowing standard .NET configuration methods to handle binding.

Confine Aspire hosting packages to the AppHost by configuring it to emit explicit environment variables for all referenced resources. This ensures application projects consume configuration transparently without requiring Aspire-specific packages.

The best way to ensure production parity with Aspire is translating AppHost resource outputs into explicit environment variables. This guarantees all configuration can be mirrored in production using standard configuration methods, eliminating hidden Aspire dependencies.

Yes, this approach configures database connection strings and blob storage endpoints by translating Aspire resource outputs into explicit environment variables. Applications consume these endpoints via standard configuration binding without Aspire client packages.