Kestrel named pipes

Author: Rick-Anderson

aspnetcore/fundamentals/servers/kestrel/endpoints.md

@@ -591,7 +591,7 @@ Kestrel's named pipe support includes advanced customization options. The [Creat
 
 This is useful, for example, in a Kestrel app that requires two pipe endpoints with different [access security](/windows/win32/ipc/named-pipe-security-and-access-rights). The `CreateNamedPipeServerStream` option can be used to create pipes with custom security settings, depending on the pipe name.
 
-:::code language="csharp" source="~/fundamentals/servers/kestrel/endpoints/samples/KestrelNamedEP/Program.cs" highlight="7-23":::
+:::code language="csharp" source="~/fundamentals/servers/kestrel/endpoints/samples/KestrelNamedEP/Program.cs" highlight="7-23" id="snippet_1":::
 
 :::moniker-end
 

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

@@ -1,3 +1,4 @@
+// <snippet_1>
 using System.IO.Pipes;
 using System.Security.AccessControl;
 using System.Security.Principal;
@@ -25,6 +26,10 @@
 static PipeSecurity CreatePipeSecurity(string pipeName)
 {
     var pipeSecurity = new PipeSecurity();
+    // configure PipeSecurity object and return;
+
+    // </snippet_1>
+    // This code to test preceding snippet compiles.
 
     // Get the current process identity.
     var currentIdentity = WindowsIdentity.GetCurrent();