CliWrap is a .NET library that provides an airtight, fluent abstraction over System.Diagnostics.Process for interacting with command-line interfaces. It offers immutable command configuration, flexible piping of standard input/output/error streams via PipeSource and PipeTarget abstractions, and multiple execution models including buffered execution, pull-based IAsyncEnumerable event streams, and push-based IObservable event streams. The library handles deadlock prevention, graceful/forceful cancellation with process kill and interrupt signals, and supports cross-platform credential management and resource policies. Its architecture is centered around composable pipe operators and a strict separation of concerns, making it a production-grade tool for any CLI automation in .NET. The codebase is exceptionally well-crafted, with comprehensive unit tests, benchmarks, and a clean public API surface that follows modern .NET conventions.
This repository serves as the primary source for .NET documentation (learn.microsoft.com/dotnet). It contains conceptual guides, API references, and runnable code samples demonstrating .NET language features, frameworks, and best practices. The repository is not a single application but a curated collection of educational materials organized by technology domain (e.g., C#, ASP.NET Core, Orleans, AI). Code samples illustrate patterns like dependency injection, logging, serialization, and data access, often with minimal, self-contained examples. Maintenance is active via GitHub Actions workflows for linting, dependency updates, and version sweeping, ensuring content stays current with .NET releases.
Refit is a .NET library that automatically generates type-safe HTTP API clients from C# interfaces decorated with attributes like [Get], [Post], [Header], [Body], and [Query]. It operates via two parallel request-building paths: a Roslyn source generator that emits inline request construction at compile time (trim/AOT-safe), and a reflection-based fallback for unsupported shapes. The library integrates deeply with Microsoft.Extensions.DependencyInjection and IHttpClientFactory, providing extension methods like AddRefitClient<T> and AddKeyedRefitClient for managed HTTP client lifecycles. It supports multiple serializers (System.Text.Json, Newtonsoft.Json, XML), content compression (gzip, Brotli, Zstandard), streaming responses (IAsyncEnumerable, JSON Lines, SSE), multipart form data, and per-request timeouts and authorization via DelegatingHandler pipelines. The architecture is modular: the core Refit package provides attributes, serialization interfaces, and the runtime GeneratedRequestRunner; Refit.HttpClientFactory adds DI integration; Refit.Newtonsoft.Json and Refit.Xml provide alternative serializers; Refit.Reflection offers the runtime request builder; and Refit.Testing supplies StubHttp and Reply for unit testing without a live server. The source generator (InterfaceStubGeneratorV2) is an incremental generator that parses interfaces and emits partial classes into the consumer assembly, using value-equatable models (ImmutableEquatableArray) for caching. The reflection path caches parsed method metadata and builds requests via delegates, ensuring parity with generated code. Key entry points include RestService.For<T>() for creating clients, AddRefitClient<T>() for DI registration, and RefitSettings for central configuration. External dependencies are minimal: System.Text.Json (built-in), Microsoft.Extensions.Http, and optionally Newtonsoft.Json or System.Xml. The library is extensively tested with unit tests, integration tests, snapshot-based generator tests, and benchmarks measuring allocation and throughput. It targets .NET 8/9/10/11 and .NET Framework 4.6.2+, with polyfills for missing BCL types.
OrchardCore is a mature, open-source modular and multi-tenant application framework and CMS built on ASP.NET Core. The codebase reveals a production-grade system with a rich extensibility model: content parts and fields with display drivers, workflow engine with activities, deployment/recipe system, multi-tenant shell contexts, and multiple search backends (Lucene, Elasticsearch, Azure AI). The frontend admin UI is implemented in Vue 3 with TypeScript (the 'Bloom' framework), providing reusable UI components and a data pipeline designer. Under the hood, it uses YesSql as a document ORM, SignalR for real-time notifications, and supports various authentication providers, localization, and media management. Despite its large surface, the architecture is cleanly separated into modules with consistent patterns (display drivers, handlers, permission providers), though some legacy deprecations and duplicate search provider code indicate manageable technical debt.
Equinox is an F# library for event-sourced systems, providing a consistent abstraction over multiple stream-based storage backends including CosmosDB, DynamoDB, EventStoreDB, MessageDB, SqlStreamStore, and an in-memory store. In production, it enables applications to define domain logic as pure decision functions that produce events, while the library manages optimistic concurrency, caching, snapshots, and retries. The core is the `Decider` pattern: an aggregate loaded from a stream, a decide function that returns events, and a fold that applies events to produce new state. Access strategies (e.g., `LatestKnownEvent`, `RollingSnapshots`, `Custom`) control how state is reconstructed from stored events, trading read cost for write cost. The architecture is modular: the `Equinox` package defines the core interfaces (`ICategory`, `IStream`, `Decider`), while separate NuGet packages implement storage adapters. The library is used as a dependency in larger applications; sample projects (`Store/Domain`, `TodoBackend`, `Tutorial`) demonstrate its use. Key entry points include the `Decider` class for command/query execution, `Category` for resolving streams, and store-specific connectors (e.g., `CosmosStoreConnector`, `DynamoStoreConnector`). A CLI tool (`Equinox.Tool`) provides provisioning, benchmarking, and data inspection commands across all stores. External dependencies are minimal per package: `Equinox` depends only on `FsCodec` for serialization; store adapters require their respective SDKs (Azure.Cosmos, AWSSDK.DynamoDBv2, EventStore.Client, Npgsql, etc.). The library includes comprehensive caching (`Equinox.Cache` wrapping `System.Runtime.Caching.MemoryCache`), metrics via Prometheus, and a load testing harness. Despite some deprecated adapters (legacy EventStore TCP, SqlStreamStore) and high complexity from multiple backends, the core patterns are clean, well-tested, and production-proven at Jet.com.
PerfView is a comprehensive performance analysis and diagnostics toolkit primarily for Windows, with growing Linux support. It collects, parses, and visualizes Event Tracing for Windows (ETW), .NET EventPipe, Linux perf, and CTF traces. The repository contains a WPF desktop application (PerfView.exe) for interactive stack, memory, and heap analysis, along with command-line tools (HeapDump, TraceParserGen, perfcollect) and a reusable library (Microsoft.Diagnostics.Tracing.TraceEvent) for programmatic trace processing. The architecture is modular, with core libraries for fast serialization, stack analysis, symbol resolution, and automated analysis. While the codebase is well-maintained and extensively tested, it contains some legacy components (custom compression, duplicated utilities) and conditional compilation that indicate moderate technical drift. The library components are the most reusable assets, offering patterns for binary serialization, caching, recursion safety, and event filtering.
BililiveRecorder is a multi-platform application for recording Bilibili (mikufans) live streams. It provides a desktop GUI (WPF), a cross-platform CLI, and a web interface (ASP.NET Core) with REST and GraphQL APIs. The core system manages room monitoring, stream capture via HTTP, danmaku (live chat) recording, and FLV file processing with a pipeline-based repair engine that fixes timestamp jumps, duplicate headers, and other stream corruption. It supports hierarchical configuration, user scripting (via embedded Jint JavaScript runtime), and webhook notifications. The application is modular: separate libraries for FLV parsing/writing (BililiveRecorder.Flv), core recording logic, toolbox utilities (fix, analyze, merge danmaku), and a web frontend with an embedded ArtPlayer-based video player. The codebase is well-structured with dependency injection, unit tests, and code generation for configuration models.
H5 is a C# to JavaScript/TypeScript transpiler that enables C# developers to target web platforms. The system consists of a compiler service (h5-compiler dotnet tool), a translator core that converts C# AST to JavaScript/TypeScript using visitor patterns and attribute-driven rules, and runtime libraries providing .NET-like functionality in JavaScript. Key features include SDK-style project integration, extensive globalization support through locale definitions, and support for JavaScript interop via attributes like [H5.External] and [H5.Template]. The toolchain processes C# source files through lexical analysis (using NRefactory), semantic analysis, translation to target language syntax, and emits JavaScript/TypeScript output with optional source maps and HTML wrappers.
This repository is a curated, community-maintained 'awesome list' for the Blazor framework (a Microsoft .NET web UI framework). It aggregates and categorizes hundreds of external resources including sample projects, tutorials, libraries, videos, articles, podcasts, tooling, books, and community links. The main entry point is the README.md, which provides a structured table of contents with shields.io badges (GitHub stars, last commit, license) for each listed resource. The repository also contains yearly archives (2017–2024) tracking historical resources, a Component-Bundle-Comparison.md that compares 16+ Blazor UI component libraries, and a CONTRIBUTING.md with contribution guidelines. The repository itself contains no executable application code or data pipelines; it is purely a documentation/curation project that serves as a discovery and reference hub for the Blazor ecosystem. The curation methodology follows a consistent pattern of categorization, metadata badges, and archival, making it a reusable template for other awesome lists. The repository is actively maintained with recent commits referencing .NET 11 previews in 2026, though the sheer volume of external links introduces inherent risk of link rot and staleness for less popular entries.
WebGPU.NET is a .NET binding library for the WebGPU API, specifically targeting WebAssembly via Blazor. It provides a low-level P/Invoke wrapper generated from Emscripten's WebGPU C header, enabling GPU compute and rendering in browser-based .NET applications. The repository includes a code generator (WebGPUGen) that parses the C header using CppAst and emits C# structs, enums, handles, delegates, and P/Invoke commands. The generated library is packaged as a NuGet package (Evergine.Bindings.WebGPU) with MSBuild integration for native WebGPU support. A Blazor WebAssembly sample (HelloTriangleWasm) demonstrates basic triangle rendering using the deprecated WGPUSwapChain API. The project is part of the Evergine ecosystem and follows the organization's binding conventions, with CI/CD pipelines and a binding manifest. While the core library is functional and the generator is effective, there are signs of technical drift: the sample uses a deprecated API, the generator has hardcoded paths and a typo, and the binding is tightly coupled to a specific Emscripten version. The repository is maintained but not actively evolving, with recent scope reduction (removal of non-browser support).
ValleyServer is a dual-mainline project that turns Stardew Valley into a persistent, unattended multiplayer server. The 2.x branch (recommended, stable) runs on a real Stardew Valley + SMAPI client, using a set of custom mods (ALOS, ServerCMD, ChatCommand, CommandWebUI, ChangeServerPort) to automate the host farmer—auto-sleeping, skipping cutscenes, handling festivals, and providing a web-based console and Docker deployment. The 3.x branch (experimental) is a standalone headless server that loads decompiled game assemblies via reflection and mocking, implements the Lidgren-based multiplayer protocol, and manages farmhand connections, warps, saving, and day transitions without any graphical client. The 3.x code is architecturally ambitious—using uninitialized objects to bypass XNA dependencies, a custom content manager that returns dummy textures/fonts, and a dedicated overnight coroutine thread—but remains incomplete (missing farming, NPCs, seasons) and is tightly coupled to a specific decompiled game version. The 2.x mods are well-documented and production-tested; the 3.x server is a technical proof-of-concept with hardcoded paths and significant fragility. The repository provides CI/CD for building both branches, issue templates, and a community Docker image.
This repository is a community-driven job board for .NET developers in Brazil, utilizing GitHub Issues as the primary platform for posting and managing job openings. There is virtually no application code; the only source files are a GitHub issue template, a Dependabot configuration, and two GitHub Actions workflows for automatic labeling and closing stale issues. The actual functionality—job posting, searching, and filtering—is entirely provided by GitHub's issue system. The repository is well-maintained with clear contribution guidelines and automated issue management, but from a software engineering perspective, there are no reusable components, architecture, or data pipelines to evaluate. It is a minimal configuration repository that effectively fulfills its community role.