microsoft-extensions-configuration

You validate .NET configuration at startup by implementing IValidateOptions or applying Data Annotations to your settings POCO, registering validation in DI, and triggering a fail-fast check during host initialization.

Strongly typed configuration binding maps configuration sections to POCO settings classes. You register options in dependency injection and inject IOptions<T> or IOptionsSnapshot<T> into your services to consume the validated, type-safe settings.

Yes, you can implement complex cross-property validation by writing a custom IValidateOptions<T> class. This validator inspects multiple properties together, allowing you to enforce advanced rules that standard Data Annotations cannot handle individually.

Named options support multiple distinct configurations within a single application by keying settings during DI registration. You resolve specific configurations at runtime using IOptionsSnapshot<T> with the corresponding name.

Yes, Microsoft.Extensions.Options is required for strongly typed configuration binding. You need a POCO settings class with a SectionName constant and a SKILL.md frontmatter-driven load sequence to operate the validation flow at startup.