A lightweight, reflection-aware formatter for debugging .NET objects, collections, and dictionaries.
EnumerablePrinter is intentionally focused on one job: printing data in a clear, predictable, human-readable format for console output, logging, and quick inspection during development. It does not try to duplicate features already provided by the .NET framework.
The library was deliberately narrowed to a single purpose:
- print common .NET values clearly
- render nested structures recursively
- show object properties in a debug-friendly way
- keep output readable and consistent
- avoid re-implementing framework features that already exist elsewhere
This makes the library easier to understand, easier to maintain, and better aligned with real debugging workflows.
- pretty-prints arrays, lists, sets, and other
IEnumerablevalues - prints
IDictionaryentries as key/value output - reflects public instance properties for complex objects
- handles
string,byte[], andIEnumerable<char>gracefully - prevents circular-reference recursion from causing runaway output
- supports console output or any
TextWriter - keeps the public API intentionally small and focused
- includes optional Python-style slicing through the separate
EnumerablePrinter.Linqproject - includes a separate Roslyn analyzer project for flagging
Print()calls in performance-sensitive code
The EnumerablePrinter.Linq project adds a focused Slice() extension for IEnumerable<T> values. It supports optional start, end, and positive step parameters, including negative indices.
Reference the project alongside EnumerablePrinter:
<ProjectReference Include="..\..\src\EnumerablePrinter.Linq\EnumerablePrinter.Linq.csproj" />Then use it with the printer:
using EnumerablePrinter.Extensions;
using EnumerablePrinter.Linq;
var numbers = new[] { 10, 20, 30, 40, 50, 60 };
numbers.Slice(start: 1, end: 4).Print();
// [20, 30, 40]
numbers.Slice(step: 2).Print();
// [10, 30, 50]
var fruits = new[] { "Apple", "Banana", "Cherry", "Date", "Elderberry" };
fruits.Slice(start: -3).Print();
// ["Cherry", "Date", "Elderberry"]Positive-index slices stream from the source; slices using negative indices buffer the source so they can resolve positions from the end. step must be greater than zero.
dotnet add package EnumerablePrinterThe repository also contains EnumerablePrinter.Analyzers, a separate netstandard2.0 Roslyn analyzer project. It defines diagnostic EP0001, which reports calls to EnumerablePrinter.Extensions.PrintExtensions.Print and suggests explicit formatting or logging instead.
The analyzer is maintained separately from the core EnumerablePrinter package. To use it from a local checkout, add a project reference to src/EnumerablePrinter.Analyzers/EnumerablePrinter.Analyzers.csproj in the consuming project.
using EnumerablePrinter.Extensions;
var numbers = new[] { 1, 2, 3, 4, 5 };
numbers.Print();
// [1, 2, 3, 4, 5]
var person = new { Name = "Wayne", Age = 42 };
person.Print();
// {Name: "Wayne", Age: 42}
var metadata = new Dictionary<string, int>
{
["One"] = 1,
["Two"] = 2
};
metadata.Print();
// {"One": 1, "Two": 2}new[] { 1, 2, 3 }.PrintToConsole();This follows the same formatting path as Print(), but makes the console intent explicit.
The formatter uses a consistent debug-printing style:
- collections render as
[ ... ] - dictionaries render as
{ "key": value } - object properties render as
PropertyName: value - strings are quoted
nullrenders asnull- circular references render as
<Circular Reference>
The project is organized around a clean release and publish split:
- release scripts handle versioning and git tagging
- deploy scripts handle build, test, packaging, and NuGet publishing
See the script guide in scripts/README.md for the full flow and dry-run usage.
The current design intentionally avoids adding collection helpers or framework duplicates. The library remains focused on the single, practical task it does well: iterating over values and printing them in a clear, debug-friendly form.
MIT
- NuGet: EnumerablePrinter on NuGet
- Repository: EnumerablePrinter on GitHub