Merge pull request #34634 from dotnet/main

Merge to Live

Author: Rick-Anderson

.github/workflows/blazor-hybrid-issue-processing.yml

@@ -17,7 +17,7 @@ jobs:
               issue_number: context.issue.number,
               owner: context.repo.owner,
               repo: context.repo.repo,
-              body: `### 💃🕺🥳 **_Happy New Year!_** 🎈🎆🍾🥂🎉
+              body: `### 🌱🐇 **_Spring is coming. Hang in there! I'm pull'in for ya!_** 🐣🌻
 
             A green dinosaur 🦖 will be along shortly to assist. *Stand-by ........*`
             })

.github/workflows/blazor-issue-processing.yml

@@ -22,7 +22,7 @@ jobs:
               issue_number: context.issue.number,
               owner: context.repo.owner,
               repo: context.repo.repo,
-              body: `### 💃🕺🥳 **_Happy New Year!_** 🎈🎆🍾🥂🎉
+              body: `### 🌱🐇 **_Spring is coming. Hang in there! I'm pull'in for ya!_** 🐣🌻
 
             *Stand-by!* ... A green dinosaur 🦖 will be along shortly to assist.`
             })

aspnetcore/fundamentals/servers/kestrel/endpoints.md

@@ -5,16 +5,14 @@ description: Learn about configuring endpoints with Kestrel, the cross-platform
 monikerRange: '>= aspnetcore-5.0'
 ms.author: tdykstra
 ms.custom: mvc
-ms.date: 06/21/2023
+ms.date: 2/4/2025
 uid: fundamentals/servers/kestrel/endpoints
 ---
 
 # Configure endpoints for the ASP.NET Core Kestrel web server
 
 [!INCLUDE[](~/includes/not-latest-version.md)]
 
-[!INCLUDE [](~/includes/not-latest-version.md)]
-
 :::moniker range=">= aspnetcore-8.0"
 
 Kestrel endpoints provide the infrastructure for listening to incoming requests and routing them to the appropriate middleware. The combination of an address and a protocol defines an endpoint.

aspnetcore/fundamentals/servers/kestrel/endpoints/samples/KestrelNamedEP/KestrelNamedEP.csproj

@@ -0,0 +1,9 @@
+<Project Sdk="Microsoft.NET.Sdk.Web">
+
+  <PropertyGroup>
+    <TargetFramework>net9.0</TargetFramework>
+    <Nullable>enable</Nullable>
+    <ImplicitUsings>enable</ImplicitUsings>
+  </PropertyGroup>
+
+</Project>

aspnetcore/fundamentals/servers/kestrel/endpoints/samples/KestrelNamedEP/Program.cs

@@ -0,0 +1,21 @@
+using System.IO.Pipes;
+
+var builder = WebApplication.CreateBuilder();
+
+builder.WebHost.ConfigureKestrel(options =>
+{
+    options.ListenNamedPipe("pipe1");
+    options.ListenNamedPipe("pipe2");
+});
+
+builder.WebHost.UseNamedPipes(options =>
+{
+    options.CreateNamedPipeServerStream = (context) =>
+    {
+        var pipeSecurity = CreatePipeSecurity(context.NamedPipeEndpoint.PipeName);
+
+        return NamedPipeServerStreamAcl.Create(context.NamedPipeEndPoint.PipeName, PipeDirection.InOut,
+            NamedPipeServerStream.MaxAllowedServerInstances, PipeTransmissionMode.Byte,
+            context.PipeOptions, inBufferSize: 0, outBufferSize: 0, pipeSecurity);
+    };
+});

aspnetcore/tutorials/razor-pages/new-field.md

@@ -19,7 +19,7 @@ In this section [Entity Framework Core (EF Core)](/ef/core/get-started/aspnetcor
 * Add a new field to the model.
 * Migrate the new field schema change to the database.
 
-The EF Core approach allows for a more agile development process. The developer works on the app's data model directly while the database schema is created and then syncronized, all without the developer having to switch contexts to and from a datbase management tool. For an overview of Entity Framework Core and its benefits, see [Entity Framework Core](/ef/core).
+The EF Core approach allows for a more agile development process. The developer works on the app's data model directly while the database schema is created and then syncronized, all without the developer having to switch contexts to and from a database management tool. For an overview of Entity Framework Core and its benefits, see [Entity Framework Core](/ef/core).
 
 Using EF Code to automatically create and track a database: