[10.0] Update Blazor node article dates for release

[guardrex]

Addresses #34437

Tom, Wade ... Just need one review on this one.

... and I'm updating the versioning INCLUDES appropriately. I think they don't activate for 9.0 articles until Nov. 10, 2026, so I'm updating my tracking notes for it.

Dates are updated for Blazor node articles using the following approach with the process that I was using prior to 2025 ...

• If an article receives a major overhaul during the year, I update the date.
• All other articles receive one date update at release each year. Therefore, Microsoft is implying that Blazor articles are up-to-date, as far as is known, each year for each .NET release.

This is only for the Blazor node with @cmastr's offline blessing ...

I’m fine with this policy. I didn’t realize that the decision we made impacted something you were already doing. I don’t think we have the same issues with a lot of unfresh content in Blazor like we do in some other places. So yes if you want to do an update each year to the ms.date, I am totally fine with that.

I still wish we had a separate metadata entry for the last major overhaul. Even if @cmastr didn't use it, it would be helpful to @danroth27 and I for scheduling article overhauls. Currently, I have weak visibility, having to rely on PR titles (they usually contain the word "overhaul" when I perform them).

---

Internal previews

Toggle expand/collapse

📄 File	🔗 Preview link
aspnetcore/blazor/advanced-scenarios.md	aspnetcore/blazor/advanced-scenarios
aspnetcore/blazor/blazor-ef-core.md	aspnetcore/blazor/blazor-ef-core
aspnetcore/blazor/call-web-api.md	aspnetcore/blazor/call-web-api
aspnetcore/blazor/components/built-in-components.md	aspnetcore/blazor/components/built-in-components
aspnetcore/blazor/components/cascading-values-and-parameters.md	aspnetcore/blazor/components/cascading-values-and-parameters
aspnetcore/blazor/components/class-libraries-and-static-server-side-rendering.md	aspnetcore/blazor/components/class-libraries-and-static-server-side-rendering
aspnetcore/blazor/components/class-libraries.md	aspnetcore/blazor/components/class-libraries
aspnetcore/blazor/components/component-disposal.md	aspnetcore/blazor/components/component-disposal
aspnetcore/blazor/components/control-head-content.md	aspnetcore/blazor/components/control-head-content
aspnetcore/blazor/components/css-isolation.md	aspnetcore/blazor/components/css-isolation
aspnetcore/blazor/components/data-binding.md	aspnetcore/blazor/components/data-binding
aspnetcore/blazor/components/dynamiccomponent.md	aspnetcore/blazor/components/dynamiccomponent
aspnetcore/blazor/components/element-component-model-relationships.md	aspnetcore/blazor/components/element-component-model-relationships
aspnetcore/blazor/components/event-handling.md	aspnetcore/blazor/components/event-handling
aspnetcore/blazor/components/generic-type-support.md	aspnetcore/blazor/components/generic-type-support
aspnetcore/blazor/components/httpcontext.md	aspnetcore/blazor/components/httpcontext
aspnetcore/blazor/components/index.md	aspnetcore/blazor/components/index
aspnetcore/blazor/components/integration-hosted-webassembly.md	aspnetcore/blazor/components/integration-hosted-webassembly
aspnetcore/blazor/components/integration.md	aspnetcore/blazor/components/integration
aspnetcore/blazor/components/js-spa-frameworks.md	aspnetcore/blazor/components/js-spa-frameworks
aspnetcore/blazor/components/layouts.md	aspnetcore/blazor/components/layouts
aspnetcore/blazor/components/lifecycle.md	aspnetcore/blazor/components/lifecycle
aspnetcore/blazor/components/overwriting-parameters.md	aspnetcore/blazor/components/overwriting-parameters
aspnetcore/blazor/components/prerender.md	aspnetcore/blazor/components/prerender
aspnetcore/blazor/hybrid/security/maui-blazor-web-identity.md	aspnetcore/blazor/hybrid/security/maui-blazor-web-identity
aspnetcore/blazor/performance/webassembly-browser-developer-tools-diagnostics.md	aspnetcore/blazor/performance/webassembly-browser-developer-tools-diagnostics
aspnetcore/blazor/performance/webassembly-event-pipe-diagnostics.md	aspnetcore/blazor/performance/webassembly-event-pipe-diagnostics
aspnetcore/blazor/performance/webassembly-runtime-performance.md	aspnetcore/blazor/performance/webassembly-runtime-performance
aspnetcore/blazor/security/blazor-web-app-with-entra.md	aspnetcore/blazor/security/blazor-web-app-with-entra
aspnetcore/blazor/security/blazor-web-app-with-windows-authentication.md	aspnetcore/blazor/security/blazor-web-app-with-windows-authentication

Note

This table shows preview links for the 30 files with the most changes. For preview links for other files in this PR, select OpenPublishing.Build Details within checks.

[Copilot]

Pull Request Overview

This PR updates the ms.date metadata field across all Blazor documentation articles in preparation for the .NET 10.0 release. The update follows the repository's annual maintenance practice of refreshing dates for all Blazor node articles at release time to indicate they have been reviewed and are current.

Key changes:

• Updates ms.date metadata from various previous dates (ranging from 2024 to 2025) to a uniform date of 11/11/2025
• Covers 145+ documentation files across the entire Blazor node
• No content changes, only metadata updates

[wadepickett]

Looks good. Thanks. Approved.

[wadepickett]

"I still wish we had a separate metadata entry for the last major overhaul."

You could do a ms.custom entry.

Alternatevely you could use an GitHub tag for PR's. GitHub copilot would generate a report of all topics that were in PR's with that tag or you can run an app against the GitHub API (Or a quick GitHub/Spark app)

[guardrex]

Thanks for those ideas, @wadepickett. I'll make a note to investigate and report back.