`TOptions` instance is validated when `IOptions<TOptions>.Value` is accessed

[deep-outcome]

Description

From https://learn.microsoft.com/en-us/aspnet/core/fundamentals/configuration/options?view=aspnetcore-8.0#validateonstart

Options validation runs the first time an IOptions<TOptions>, IOptionsSnapshot<TOptions>, or IOptionsMonitor<TOptions> implementation is created.

Options validation runs when IOptions<TOptions>.Value is accessed not when IOptions<TOptions> is created. Similar applies for IOptionsSnapshot<TOptions> & IOptionsMonitor<TOptions>. See also https://source.dot.net/#Microsoft.Extensions.Options/OptionsFactory.cs,55.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/configuration/options?view=aspnetcore-8.0

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/fundamentals/configuration/options.md

Document ID

dc7e3449-650b-d117-5eac-69e5ccb250cb

Article author

@tdykstra

[tdykstra]

Thanks for reporting that. We'll revise the wording the next time we update the article, or you're welcome to submit a Pull Request to address the issue.

[deep-outcome]

I picked the latter – #33844. Please, redact this. On my local env it is impossible to validate code references and I am not familiar with project technical writers' customs.

[tdykstra]

Thanks for the PR, I'll fix the xref links, probably Monday.

[tdykstra]

This was fixed by #33844