dotnet/Nerdbank.Streams

Latest recorded source activity: October 11, 2026 at 03:33

SkillsMP catalog refreshed: November 5, 2026 at 19:57

skills collected: 1

GitHub stars: 723
GitHub forks: 77

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/dotnet/Nerdbank.Streams.

Repository README

Repository README source: README.md

Read the source README

Expand full README

# Specialized .NET Stream classes [![NuGet package](https://img.shields.io/nuget/v/Nerdbank.Streams.svg)](https://www.nuget.org/packages/Nerdbank.Streams) [![Build Status](https://dev.azure.com/andrewarnott/OSS/_apis/build/status/Nerdbank.Streams)](https://dev.azure.com/andrewarnott/OSS/_build/latest?definitionId=14) [![codecov](https://codecov.io/gh/AArnott/Nerdbank.Streams/branch/main/graph/badge.svg)](https://codecov.io/gh/AArnott/Nerdbank.Streams) *Enhanced streams for communication in-proc or across the Internet.* ## Features 1. [`SimplexStream`](https://dotnet.github.io/Nerdbank.Streams/docs/SimplexStream.html) is meant to allow two parties to communicate *one direction*. Anything written to the stream can subsequently be read from it. You can share this `Stream` with any two parties (in the same AppDomain) and one can send messages to the other. 1. [`FullDuplexStream`](https://dotnet.github.io/Nerdbank.Streams/docs/FullDuplexStream.html) creates a pair of bidirectional streams for in-proc two-way communication; it also creates a single bidirectional stream from two unidirectional streams. 1. [`MultiplexingStream`](https://dotnet.github.io/Nerdbank.Streams/docs/MultiplexingStream.html) allows you to split any bidirectional .NET Stream into many sub-streams (called channels). This allows two parties to establish just one transport stream (e.g. named pipe or web socket) and use it for many independent protocols. For example, one might set up JSON-RPC on one channel and use other channels for efficient binary transfers. 1. [`AsStream()`](https://dotnet.github.io/Nerdbank.Streams/docs/AsStream.html) wraps a `WebSocket`, `System.IO.Pipelines.PipeReader`, `System.IO.Pipelines.PipeWriter`, or `System.IO.Pipelines.IDuplexPipe` with a `System.IO.Stream` for reading and/or writing. 1. [`UsePipe()`](https://dotnet.github.io/Nerdbank.Streams/docs/UsePipe.html) enables reading from and writing to a `Stream` or `WebSocket` using the `PipeReader` and `PipeWriter` APIs. 1. [`Stream.ReadSlice(long)`](https://dotnet.github.io/Nerdbank.Streams/docs/ReadSlice.html) creates a sub-stream that ends after a given number of bytes. 1. [`PipeReader.ReadSlice(long)`](https://dotnet.github.io/Nerdbank.Streams/docs/ReadSlice.html) creates a sub-`PipeReader` that ends after a given number of bytes. 1. [`MonitoringStream`](https://dotnet.github.io/Nerdbank.Streams/docs/MonitoringStream.html) wraps another Stream and raises events for all I/O calls so you can monitor and/or trace the data as it goes by. 1. [`WriteSubstream` and `ReadSubstream`](https://dotnet.github.io/Nerdbank.Streams/docs/Substream.html) allow you to serialize data of an unknown length as part of a larger stream, and later deserialize it such in reading the substream, you cannot read more bytes than were written to it. 1. [`Sequence<T>`](https://dotnet.github.io/Nerdbank.Streams/docs/Sequence.html) is a builder for `ReadOnlySequence<T>`. 1. [`PrefixingBufferWriter<T>`](https://dotnet.github.io/Nerdbank.Streams/docs/PrefixingBufferWriter.html) wraps another `IBufferWriter<T>` to allow for prefixing some header to the next written buffer, which may be arbitrarily long. 1. [`BufferTextWriter`](https://dotnet.github.io/Nerdbank.Streams/docs/BufferTextWriter.html) is a `TextWriter`-derived type that can write directly to any `IBufferWriter<byte>`, making it more reusable than `StreamWriter` and thus allows for alloc-free writing across many writers. 1. [`SequenceTextReader`](https://dotnet.github.io/Nerdbank.Streams/docs/SequenceTextReader.html) is a `TextReader`-derived type that can read directly from any `ReadOnlySequence<byte>`, making it more reusable than `StreamReader` and thus allows for alloc-free reading across many sequences. 1. [`DuplexPipe`](https://dotnet.github.io/Nerdbank.Streams/docs/DuplexPipe.html) is a trivial implementation of `IDuplexPipe`. 1. [`Stream.ReadBlockAsync`](https://dotnet.github.io/Nerdbank.Streams/docs/ReadBlockAsync.html) guarantees to fill the supplied buffer except under certain documented conditions, instead of the regular `ReadAsync` guarantee of supplying at least 1 byte. ## .NET Foundation This project is supported by the [.NET Foundation](https://dotnetfoundation.org).

Loading the repository README…

Skills in this repository

classification pending

skill

occupation

description

updated

testing

unclassified

Provides guidance and instructions for writing, running and filtering tests.

2026-10-11

Showing 1 of 1 collected skill.