Modern .NET Configuration Practices
summary
Demos and code live on GitHub and VS Code, showing concrete migrations: replace baked-in web.config with layered JSON, environment variables, IConfiguration providers, and Azure App Configuration; use user secrets for dev, managed identities instead of connection strings, and Key Vault when needed. Implements strongly typed settings with the Options pattern, uses IOptionsMonitor for live reload and validation-on-start to fail bad configs, and wires Aspire (CLI + bicep output, service discovery) for reproducible local-to-cloud deployments.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:08Modern .NET config matters
- 4:42Legacy to modern config
- 8:54Config sources and providers
- 15:18User secrets and environment variables
- 18:11Command line overrides
- 21:20Strongly typed config
- 23:06IOptions explained
- 34:52Testing config in-memory
- 35:57Config validation
- 41:53Secrets with Key Vault
- 47:33Feature flags in App Config
- 49:02Aspire config intro
- 53:16Aspire orchestration
- 59:36Best practices & Q&A
related talks
01h 01mModern .NET Configuration Practices
44mModern NET Configuration Practices
01h 13mBuilding Confident Application Systems with .NET Aspire: From Dev to Deployment
01h 12mHarness the Power of Azure with Visual Studio
27mModernize Your .NET Skills
56mEasier infrastructure and safer secrets with Pulumi, Azure, and .Net Core
01h 01mAdvanced Cloud Native Development with .NET Aspire
01h 19mAsk Me Anything - Demystify Cloud-Native Development with .NET Aspire