From 883a2e062138cddb18f6ad7b203c83f841ad9ef4 Mon Sep 17 00:00:00 2001 From: Youssef Fahmy Date: Fri, 7 Aug 2026 10:31:36 +0200 Subject: [PATCH 1/2] Update Blazor form validation for MEV experimental status in 11 --- aspnetcore/blazor/forms/validation.md | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/aspnetcore/blazor/forms/validation.md b/aspnetcore/blazor/forms/validation.md index 576f51dbcc24..69603c1ffe73 100644 --- a/aspnetcore/blazor/forms/validation.md +++ b/aspnetcore/blazor/forms/validation.md @@ -2625,10 +2625,6 @@ public class ShipDescription ## Use validation models from a different assembly - - For model validation defined in a different assembly, such as a library or the `.Client` project of a Blazor Web App: * If the library is a plain class library (it isn't based on the `Microsoft.NET.Sdk.Web` or `Microsoft.NET.Sdk.Razor` SDKs), add a package reference to the library for the [`Microsoft.Extensions.Validation` NuGet package](https://www.nuget.org/packages/Microsoft.Extensions.Validation). Additional steps are required for plain class libraries, which are described later in this section. @@ -2665,9 +2661,7 @@ builder.Services.AddValidationForTypesInClient(); builder.Services.AddValidation(); ``` - +:::moniker range="= aspnetcore-10.0" The new attributes from the `Microsoft.Extensions.Validation` package ( and ) are published as *experimental* in .NET 10. The package is intended to provide a new shared infrastructure for validation features across frameworks, and publishing experimental types provides greater flexibility for the final design of the public API for better support in consuming frameworks. @@ -2721,6 +2715,8 @@ Whichever approach is adopted, denote the presence of the workaround for a futur :::moniker-end +:::moniker-end + ## Enable the submit button based on form validation To enable and disable the submit button based on form validation, the following example: From 5484ad84dccb404ac0805d2ab0df3bd8fd303a1c Mon Sep 17 00:00:00 2001 From: Youssef Fahmy Date: Fri, 7 Aug 2026 10:44:32 +0200 Subject: [PATCH 2/2] Update validation.md --- aspnetcore/blazor/forms/validation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aspnetcore/blazor/forms/validation.md b/aspnetcore/blazor/forms/validation.md index 69603c1ffe73..730a619caf70 100644 --- a/aspnetcore/blazor/forms/validation.md +++ b/aspnetcore/blazor/forms/validation.md @@ -2661,6 +2661,8 @@ builder.Services.AddValidationForTypesInClient(); builder.Services.AddValidation(); ``` +:::moniker-end + :::moniker range="= aspnetcore-10.0" The new attributes from the `Microsoft.Extensions.Validation` package ( and ) are published as *experimental* in .NET 10. The package is intended to provide a new shared infrastructure for validation features across frameworks, and publishing experimental types provides greater flexibility for the final design of the public API for better support in consuming frameworks. @@ -2715,8 +2717,6 @@ Whichever approach is adopted, denote the presence of the workaround for a futur :::moniker-end -:::moniker-end - ## Enable the submit button based on form validation To enable and disable the submit button based on form validation, the following example: