Merge pull request #35491 from dotnet/main

Author: guardrex

aspnetcore/blazor/host-and-deploy/webassembly/azure-static-web-apps.md

@@ -14,6 +14,20 @@ uid: blazor/host-and-deploy/webassembly/azure-static-web-apps
 
 This article explains how to host and deploy standalone Blazor WebAssembly with [Microsoft Azure Static Web Apps](https://azure.microsoft.com/products/app-service/static).
 
+## App configuration
+
+To ensure that requests for any path return `index.html`, set a navigation fallback route.
+
+Create a file named `staticwebapp.config.json` in the project's root folder with the following content:
+
+```json
+{
+  "navigationFallback": {
+    "rewrite": "/index.html"
+  }
+}
+```
+
 ## Deploy from Visual Studio
 
 To deploy from Visual Studio, create a publish profile for Azure Static Web Apps:

aspnetcore/blazor/performance/rendering.md

@@ -22,17 +22,21 @@ At runtime, components exist in a hierarchy. A root component (the first compone
 
 1. The event is dispatched to the component that rendered the event's handler. After executing the event handler, the component is rerendered.
 1. When a component is rerendered, it supplies a new copy of parameter values to each of its child components.
-1. After a new set of parameter values is received, each component decides whether to rerender. Components rerender if the parameter values may have changed, for example, if they're mutable objects.
+1. After a new set of parameter values is received, Blazor decides whether to rerender the component. Components rerender if [`ShouldRender`](xref:blazor/components/rendering#suppress-ui-refreshing-shouldrender) returns `true`, which is the default behavior unless overridden, and the parameter values may have changed, for example, if they're mutable objects.
 
 The last two steps of the preceding sequence continue recursively down the component hierarchy. In many cases, the entire subtree is rerendered. Events targeting high-level components can cause expensive rerendering because every component below the high-level component must rerender.
 
 To prevent rendering recursion into a particular subtree, use either of the following approaches:
 
-* Ensure that child component parameters are of primitive immutable types, such as `string`, `int`, `bool`, `DateTime`, and other similar types. The built-in logic for detecting changes automatically skips rerendering if the primitive immutable parameter values haven't changed. If you render a child component with `<Customer CustomerId="item.CustomerId" />`, where `CustomerId` is an `int` type, then the `Customer` component isn't rerendered unless `item.CustomerId` changes.
-* Override <xref:Microsoft.AspNetCore.Components.ComponentBase.ShouldRender%2A>:
-  * To accept nonprimitive parameter values, such as complex custom model types, event callbacks, or <xref:Microsoft.AspNetCore.Components.RenderFragment> values.
+* Ensure that child component parameters are of specific immutable types&dagger;, such as `string`, `int`, `bool`, and `DateTime`. The built-in logic for detecting changes automatically skips rerendering if the immutable parameter values haven't changed. If you render a child component with `<Customer CustomerId="item.CustomerId" />`, where `CustomerId` is an `int` type, then the `Customer` component isn't rerendered unless `item.CustomerId` changes.
+* Override [`ShouldRender`](xref:blazor/components/rendering#suppress-ui-refreshing-shouldrender), returning `false`:
+  * When parameters are nonprimitive types or unsupported immutable types&dagger;, such as complex custom model types or <xref:Microsoft.AspNetCore.Components.RenderFragment> values, and the parameter values haven't changed,
   * If authoring a UI-only component that doesn't change after the initial render, regardless of parameter value changes.
 
+&dagger;For more information, see [the change detection logic in Blazor's reference source (`ChangeDetection.cs`)](https://github.com/dotnet/aspnetcore/blob/main/src/Components/Components/src/ChangeDetection.cs).
+
+[!INCLUDE[](~/includes/aspnetcore-repo-ref-source-links.md)]
+
 The following airline flight search tool example uses private fields to track the necessary information to detect changes. The previous inbound flight identifier (`prevInboundFlightId`) and previous outbound flight identifier (`prevOutboundFlightId`) track information for the next potential component update. If either of the flight identifiers change when the component's parameters are set in [`OnParametersSet`](xref:blazor/components/lifecycle#after-parameters-are-set-onparameterssetasync), the component is rerendered because `shouldRender` is set to `true`. If `shouldRender` evaluates to `false` after checking the flight identifiers, an expensive rerender is avoided:
 
 ```razor

aspnetcore/blazor/performance/webassembly-browser-developer-tools-diagnostics.md

@@ -102,10 +102,10 @@ Filter | Description
 `+EXPR` | Includes expression
 `-EXPR` | Excludes expression
 
-In the following example, profiled methods are filtered to the app's namespace, which is represented by the `{APP NAMESPACE}` placeholder:
+In the following example, profiled methods are filtered to the app's namespace `SampleApp` and sampling interval is 50ms.
 
 ```xml
-<WasmProfilers>browser:callspec=N:{APP NAMESPACE};</WasmProfilers>
+<WasmProfilers>browser:callspec=N:SampleApp,interval=50</WasmProfilers>
 ```
 
 ## Additional resources

aspnetcore/client-side/libman/samples/LibManSample/LibManSample.csproj

@@ -1,14 +1,13 @@
 <Project Sdk="Microsoft.NET.Sdk.Web">
 
   <PropertyGroup>
-    <TargetFramework>netcoreapp2.1</TargetFramework>
-    <TypeScriptToolsVersion>3.0</TypeScriptToolsVersion>
+    <TargetFramework>net8.0</TargetFramework>
+    <TypeScriptToolsVersion>Latest</TypeScriptToolsVersion>
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.AspNetCore.App" />
     <!-- <snippet_RestoreOnBuildPackage> -->
-    <PackageReference Include="Microsoft.Web.LibraryManager.Build" Version="1.0.113" />
+    <PackageReference Include="Microsoft.Web.LibraryManager.Build" Version="3.0.71" />
     <!-- </snippet_RestoreOnBuildPackage> -->
   </ItemGroup>
 

aspnetcore/client-side/libman/samples/LibManSample/Startup.cs

@@ -6,19 +6,20 @@
 using Microsoft.AspNetCore.Hosting;
 using Microsoft.AspNetCore.Http;
 using Microsoft.Extensions.DependencyInjection;
+using Microsoft.Extensions.Hosting;
 
 namespace LibManSample
 {
     public class Startup
     {
         // This method gets called by the runtime. Use this method to add services to the container.
         // For more information on how to configure your application, visit https://go.microsoft.com/fwlink/?LinkID=398940
-        public void ConfigureServices(IServiceCollection services)
+        public void ConfigureServices()
         {
         }
 
         // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
-        public void Configure(IApplicationBuilder app, IHostingEnvironment env)
+        public void Configure(IApplicationBuilder app, IHostEnvironment env)
         {
             if (env.IsDevelopment())
             {

aspnetcore/client-side/libman/samples/LibManSample/libman.json

@@ -3,7 +3,7 @@
   "defaultProvider": "cdnjs",
   "libraries": [
     {
-      "library": "jquery@3.3.1",
+      "library": "jquery@3.7.1",
       "files": [
         "jquery.min.js",
         "jquery.js",
@@ -13,17 +13,8 @@
     },
     {
       "provider": "unpkg",
-      "library": "bootstrap@4.1.3",
+      "library": "bootstrap@5.3.6",
       "destination": "wwwroot/lib/bootstrap/"
-    },
-    {
-      "provider": "filesystem",
-      "library": "C:\\temp\\lodash\\",
-      "files": [
-        "lodash.js",
-        "lodash.min.js"
-      ],
-      "destination": "wwwroot/lib/lodash/"
     }
   ]
-}
+}

aspnetcore/fundamentals/minimal-apis.md

@@ -5,7 +5,7 @@ description: Provides an overview of minimal APIs in ASP.NET Core
 ms.author: wpickett
 content_well_notification: AI-contribution
 monikerRange: '>= aspnetcore-6.0'
-ms.date: 02/07/2025
+ms.date: 05/19/2025
 uid: fundamentals/minimal-apis
 ai-usage: ai-assisted
 ---
@@ -16,7 +16,7 @@ ai-usage: ai-assisted
 
 [!INCLUDE[](~/includes/not-latest-version.md)]
 
-:::moniker range=">= aspnetcore-8.0"
+:::moniker range=">= aspnetcore-10.0"
 
 This document:
 
@@ -28,7 +28,7 @@ The minimal APIs consist of:
 * [WebApplication and WebApplicationBuilder](xref:fundamentals/minimal-apis/webapplication)
 * [Route Handlers](xref:fundamentals/minimal-apis/route-handlers)
 
-[!INCLUDE[](~/fundamentals/minimal-apis/includes/webapplication8.md)]
+[!INCLUDE[](~/fundamentals/minimal-apis/includes/webapplication10.md)]
 
 ## ASP.NET Core Middleware
 
@@ -68,7 +68,50 @@ The <xref:System.Delegate> arguments passed to these methods are called "route h
 
 ## Parameter binding
 
-[!INCLUDE [](~/fundamentals/minimal-apis/includes/parameter-binding8.md)]
+[!INCLUDE [](~/fundamentals/minimal-apis/includes/parameter-binding10.md)]
+
+## Validation support in Minimal APIs
+
+Support for validation in Minimal APIs is now available. This feature allows you to request validation of data sent to your API endpoints. Enabling validation allows the ASP.NET Core runtime to perform any validations defined on the:
+
+* Query
+* Header
+* Request body
+
+Validations are defined using attributes in the [`DataAnnotations`](xref:System.ComponentModel.DataAnnotations) namespace. 
+
+When a parameter to a Minimal API endpoint is a class or record type, validation attributes are automatically applied. For example:
+
+```csharp
+public record Product(
+    [Required] string Name,
+    [Range(1, 1000)] int Quantity);
+```
+Developers customize the behavior of the validation system by:
+
+* Creating custom [`[Validation]`](xref:System.ComponentModel.DataAnnotations.ValidationAttribute) attribute implementations.
+* Implementing the [`IValidatableObject`](xref:System.ComponentModel.DataAnnotations.IValidatableObject) interface for complex validation logic.
+
+If validation fails, the runtime returns a 400 Bad Request response with details of the validation errors.
+
+### Enable built-in validation support for minimal APIs
+
+Enable the built-in validation support for minimal APIs by calling the `AddValidation` extension method to register the required services in the service container for your application:
+
+```csharp
+builder.Services.AddValidation();
+```
+
+The implementation automatically discovers types that are defined in minimal API handlers or as base types of types defined in minimal API handlers. An endpoint filter performs validation on these types and is added for each endpoint.
+
+Validation can be disabled for specific endpoints by using the `DisableValidation` extension method, as in the following example:
+
+```csharp
+app.MapPost("/products",
+    ([EvenNumber(ErrorMessage = "Product ID must be even")] int productId, [Required] string name)
+        => TypedResults.Ok(productId))
+    .DisableValidation();
+```
 
 ## Responses
 
@@ -285,5 +328,7 @@ The following code disables `ValidateScopes` and `ValidateOnBuild` in `Developme
 
 :::moniker-end
 
+[!INCLUDE[](~/fundamentals/minimal-apis/includes/minimal-apis9.md)]
+[!INCLUDE[](~/fundamentals/minimal-apis/includes/minimal-apis8.md)]
 [!INCLUDE[](~/fundamentals/minimal-apis/includes/minimal-apis7.md)]
 [!INCLUDE[](~/fundamentals/minimal-apis/includes/minimal-apis6.md)]