diff --git a/xml/System.IO.Pipes/NamedPipeServerStream.xml b/xml/System.IO.Pipes/NamedPipeServerStream.xml index 02a98c37184..97c0c744518 100644 --- a/xml/System.IO.Pipes/NamedPipeServerStream.xml +++ b/xml/System.IO.Pipes/NamedPipeServerStream.xml @@ -52,14 +52,18 @@ objects. - Any process can act as either a named pipe server or client, or both. +Named pipes provide one-way or duplex pipes for communication between a pipe server and one or more pipe clients. Named pipes can be used for interprocess communication locally or over a network. A single pipe name can be shared by multiple objects. + +Any process can act as either a named pipe server or client, or both. + +With regards to thread safety for reading and writing, up to a single reader and a single writer can use an instance concurrently. ## Examples - The following example demonstrates a way to send a string from a parent process to a child process on the same computer using named pipes. This example creates a object in a parent process with a value of . The server then waits for a object in a child process to connect to it. In this example, both processes are on the same computer and the object has a value of . The parent process then sends a user-supplied string to the child process. The string is displayed to the console. - This example is for the server process, which uses the class. For the entire code example, including the code for both the pipe client and server, see [How to: Use Named Pipes for Network Interprocess Communication](/dotnet/standard/io/how-to-use-named-pipes-for-network-interprocess-communication). +The following example demonstrates a way to send a string from a parent process to a child process on the same computer using named pipes. This example creates a object in a parent process with a value of . The server then waits for a object in a child process to connect to it. In this example, both processes are on the same computer and the object has a value of . The parent process then sends a user-supplied string to the child process. The string is displayed to the console. + +This example is for the server process, which uses the class. For the entire code example, including the code for both the pipe client and server, see [How to: Use Named Pipes for Network Interprocess Communication](/dotnet/standard/io/how-to-use-named-pipes-for-network-interprocess-communication). :::code language="csharp" source="~/snippets/csharp/System.IO.Pipes/NamedPipeServerStream/Overview/Program.cs" id="Snippet01"::: :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_CLR_System/system.IO.Pipes.NamedPipeServerStream_Sample1/vb/program.vb" id="Snippet01":::