{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is the default priority order of configuration sources in ASP.NET Core?","acceptedAnswer":{"@type":"Answer","text":"Configuration sources are read in a specific order where later sources override earlier ones. Environment variables have the highest priority, followed by appsettings.{Environment}.json, then appsettings.json. User Secrets is only loaded in Development environment and has lower priority than environment variables."}},{"@type":"Question","name":"What is the main benefit of using separate appsettings.{Environment}.json files?","acceptedAnswer":{"@type":"Answer","text":"appsettings.{Environment}.json files allow defining environment-specific configurations without changing code. For example, a local connection string in Development and an Azure connection string in Production. This avoids hardcoding values or modifying code during deployment."}},{"@type":"Question","name":"What is the main role of User Secrets in ASP.NET Core?","acceptedAnswer":{"@type":"Answer","text":"User Secrets stores secrets (API keys, connection strings) in a local JSON file located outside the project, typically in the user directory. This prevents accidentally committing secrets to Git. User Secrets is only loaded in Development environment and should never be used in production."}},{"@type":"Question","name":"What is the key difference between IOptions and IOptionsSnapshot?","acceptedAnswer":{"@type":"Answer","text":"IOptions is singleton and reads configuration at startup once. IOptionsSnapshot is scoped (per request) and re-reads configuration on each request, allowing detection of changes in appsettings.json without restarting the app. Use IOptionsSnapshot for configs that may change frequently."}},{"@type":"Question","name":"When should you use IOptionsMonitor instead of IOptionsSnapshot?","acceptedAnswer":{"@type":"Answer","text":"IOptionsMonitor is singleton and allows reacting to configuration changes via OnChange. This is useful for singleton services (e.g., cache, logger) that need to adjust their behavior when appsettings.json changes. IOptionsSnapshot only works in an HTTP scope and cannot be injected into a singleton."}},{"@type":"Question","name":"How to automatically bind a section of appsettings.json to a POCO class?","acceptedAnswer":{"@type":"Answer","text":"Automatic binding is done via Configure(GetSection(\"SectionName\")) which maps JSON properties to C# properties. Then, inject IOptions into services to access typed values. This avoids magic strings and provides build-time validation."}},{"@type":"Question","name":"What is the format of environment variable keys to override hierarchical JSON configuration?","acceptedAnswer":{"@type":"Answer","text":"Environment variables use double underscore __ to represent JSON hierarchy levels because some OS don't accept dots in variable names. For example, \"ConnectionStrings__DefaultConnection\" corresponds to { \"ConnectionStrings\": { \"DefaultConnection\": \"...\" } } in JSON."}},{"@type":"Question","name":"How to automatically validate configuration options at application startup?","acceptedAnswer":{"@type":"Answer","text":"ValidateDataAnnotations() enables validation via DataAnnotations ([Required], [Range], etc.) and ValidateOnStart() forces validation at startup instead of first use. This allows fail-fast if configuration is invalid rather than waiting for the first HTTP request. Validation can also be custom via Validate()."}},{"@type":"Question","name":"By default, what happens when appsettings.json is modified while the application is running?","acceptedAnswer":{"@type":"Answer","text":"ASP.NET Core enables automatic reloading of appsettings.json files by default (reloadOnChange: true). IOptionsSnapshot and IOptionsMonitor retrieve new values, but IOptions remains frozen. In production, disable reload if configurations should never change during execution to avoid inconsistent behaviors."}},{"@type":"Question","name":"How to define the execution environment of an ASP.NET Core application?","acceptedAnswer":{"@type":"Answer","text":"ASPNETCORE_ENVIRONMENT determines which appsettings.{Environment}.json file will be loaded and if User Secrets will be enabled. Standard values are Development, Staging, Production. In Development, features like Developer Exception Page and User Secrets are enabled. In Production, these features are disabled for security."}},{"@type":"Question","name":"What is the difference between Configuration.GetValue(\"Key\") and Configuration.GetSection(\"Key\")?","acceptedAnswer":{"@type":"Answer","text":"GetValue(\"Key\") reads a simple value and converts it to type T (e.g., int, bool, string). GetSection(\"Key\") returns an IConfigurationSection object that allows navigating sub-sections or binding to a class via Bind(). Use GetValue for simple scalar values, GetSection for complex objects."}},{"@type":"Question","name":"What is the role of launchSettings.json in ASP.NET Core configuration?","acceptedAnswer":{"@type":"Answer","text":"launchSettings.json is used by Visual Studio and dotnet run to define startup profiles (IIS Express, Kestrel) and local environment variables. This file is never deployed to production and is only for local development. Real production settings should be in appsettings.Production.json or environment variables."}},{"@type":"Question","name":"Why use Azure Key Vault instead of environment variables for secrets in production?","acceptedAnswer":{"@type":"Answer","text":"Azure Key Vault centralizes secret management with automatic rotation, access auditing, Azure AD-based access control and hardware encryption (HSM). This reduces compromise risk compared to environment variables which can be exposed via process dumps or logs. ASP.NET Core integration is done via Azure.Extensions.AspNetCore.Configuration.Secrets package."}},{"@type":"Question","name":"How to configure multiple option instances for the same POCO class with different values?","acceptedAnswer":{"@type":"Answer","text":"Named Options allow having multiple configurations for the same class via a unique name. For example, multiple DB connections or HTTP clients. Configure(\"Name\", ...) registers a named config, then IOptionsSnapshot.Get(\"Name\") or IOptionsMonitor.Get(\"Name\") retrieves the desired instance. Useful for multi-tenancy or multiple third-party APIs."}},{"@type":"Question","name":"What is the best practice for managing sensitive secrets (API keys, passwords) in production?","acceptedAnswer":{"@type":"Answer","text":"Secrets should never be in appsettings.json files (risk of accidental commit) or hardcoded. In production, use a secret manager (Azure Key Vault, AWS Secrets Manager) with automatic rotation and auditing. In development, User Secrets is sufficient. Environment variables are acceptable but less secure than secret managers."}},{"@type":"Question","name":"When should you inject IConfiguration directly instead of IOptions?","acceptedAnswer":{"@type":"Answer","text":"IOptions provides strong typing, validation and separation of concerns. Injecting IConfiguration directly creates tight coupling with the configuration system and loses typing. Reserve IConfiguration for cases where config structure is truly dynamic or for configuring options themselves. In 90% of cases, prefer IOptions."}},{"@type":"Question","name":"What happens if a configuration key exists in both appsettings.json AND an environment variable?","acceptedAnswer":{"@type":"Answer","text":"Configuration providers are loaded in a specific order where later ones override earlier ones. Environment variables are added after appsettings.json so they win. This allows easily overriding config in production via env vars without touching files. The exact order is defined in CreateDefaultBuilder."}},{"@type":"Question","name":"How to add a custom configuration source (e.g., database) to the configuration system?","acceptedAnswer":{"@type":"Answer","text":"Custom configuration sources implement IConfigurationSource (factory) and IConfigurationProvider (data loading). builder.Configuration.Add() registers the source which will be loaded at build. Useful for loading config from DB, external API or custom format. Watch for circular dependencies if the custom source itself requires configuration."}},{"@type":"Question","name":"How to bind a JSON array from appsettings.json to a List property in an options class?","acceptedAnswer":{"@type":"Answer","text":"Binding natively supports JSON arrays to List, T[], IEnumerable. Example: { \"AllowedHosts\": [\"localhost\", \"example.com\"] } automatically binds to public List AllowedHosts { get; set; }. Array indices can also be overridden via env vars with syntax AllowedHosts__0, AllowedHosts__1."}},{"@type":"Question","name":"What impact does automatic reloading of appsettings.json (reloadOnChange: true) have on production performance?","acceptedAnswer":{"@type":"Answer","text":"Reloading monitors the file via FileSystemWatcher (low CPU overhead). The main risk is inconsistency: one request may read old config, the next the new one. If config is static in production, disable reloadOnChange via WebApplicationBuilder.Configuration.Sources to avoid surprises. In dev, reload is useful for testing without restart."}}]}