OptionsBuilderExtensions.ValidateOnStart is available for earlier .NET versions than documented

[mattflaschen]

Type of issue

Missing information

Description

OptionsBuilderExtensions.ValidateOnStart is documented as available for .NET 10 (package-provided) and .NET 11 (package-provided).

In fact, it is also available at least in .NET 8, as confirmed both by building a .NET 8 project (without using any 10.* libraries) using ValidateOnStart() and looking at the .NET code (OptionsBuilderExtensions.cs in v8.0.0).

Page URL

https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.dependencyinjection.optionsbuilderextensions.validateonstart?view=net-10.0-pp

Content source URL

https://github.com/dotnet/dotnet-api-docs/blob/main/xml/Microsoft.Extensions.DependencyInjection/OptionsBuilderExtensions.xml

Document Version Independent Id

10b519ef-800a-74b4-fea6-31ba2dc5a0eb

Platform Id

f4f0717a-a60a-fe24-4d83-2630a8e2dab0

Article author

@dotnet-bot

[gewarren]

This is a known limitation of the API reference docs site. Only the most recent package (https://www.nuget.org/packages/Microsoft.Extensions.Options/11.0.0-preview.3.26207.106#supportedframeworks-body-tab) is used to display the applicable versions, and for this package, the earliest TFM it supports is .NET 10. But if you look at the Frameworks tab for 10.x versions of the same package, you can see that it targets .NET 8. If an API is also part of the shared framework, then I believe the "package" version takes precedence for the docs site.