Modern NET Configuration Practices
summary
Code-heavy demos and GitHub samples show modern .NET unifying JSON, env vars, command-line, Azure Key Vault, and Azure App Configuration feature flags into a single IConfiguration; examples demonstrate binding nested objects, IOptions vs IOptionsSnapshot vs IOptionsMonitor (snapshot/monitor reload, IOptions does not), startup validation that fails fast on invalid values, user secrets for local dev, App Configuration refresh via a sentinel, and Aspire local orchestration that injects connection strings and service endpoints so the multi-service demos actually run end-to-end.
AI-written summary · about
chapters (13)
- 0:00🚀 Build Stuff Conference – Get Your Tickets!
- 0:18Introduction and context: why configuration matters
- 2:00The old .NET Framework approach: config files, transforms, and pain
- 5:22Binding config to nested objects and hierarchies
- 6:18Generic Host defaults and built-in configuration behavior
- 11:30Accessing nested config with colon syntax
- 17:27Introduction to the options pattern
- 18:10IOptions, IOptionsSnapshot, and IOptionsMonitor explained
- 28:17Validation with data annotations
- 32:34Introduction to Aspire and distributed app orchestration
- 36:22Secrets and production guidance: avoid storing credentials in config files
- 37:12Managed identity, Key Vault, and Kubernetes secret integrations
- 38:05Final thoughts and Q&A
related talks
01h 01mModern .NET Configuration Practices
01h 02mModern .NET Configuration Practices
01h 01mASP.NET Basics for Experts
01h 11mASP.NET Basics for Experts
53mDynamic Behavior of the Options Pattern
56mEasier infrastructure and safer secrets with Pulumi, Azure, and .Net Core
01h 19mAsk Me Anything - Demystify Cloud-Native Development with .NET Aspire
01h 13mBuilding Confident Application Systems with .NET Aspire: From Dev to Deployment