Modern .NET Configuration Practices
summary
Covers concrete practices: use JSON, environment variables, command-line, Azure App Config and Key Vault as configuration providers; bind hierarchical settings to classes for strongly typed configuration; use IOptions, IOptionsMonitor and IOptionsSnapshot with their reload and lifetime tradeoffs (IOptions doesn’t reload, Monitor does); validate on startup with data annotations or custom validators; use post-configure to correct bad values; inspect precedence and provenance with GetDebugView; demos (GitHub repo, setup scripts, Aspire developer loop) run and show live refreshes and working integrations.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:55Evolution of configuration
- 4:20Legacy configuration
- 5:58Modern .NET configuration
- 11:48Core configuration features
- 20:13Advanced binding and types
- 30:27Options pattern
- 44:02Validation and best practices
- 51:22Azure app configuration
- 55:51Aspire and conclusion
related talks
01h 02mModern .NET Configuration Practices
44mModern NET Configuration Practices
53mDynamic Behavior of the Options Pattern
01h 02m10 Opinions For Creating More Maintainable .NET Apps
01h 13mBuilding Confident Application Systems with .NET Aspire: From Dev to Deployment
18mEverything-as-Code: It's time to fix configurations
27mModernize Your .NET Skills
19mConfig as Code