This repository is a comprehensive .NET SDK for integrating with the WeChat (Weixin) ecosystem, covering Official Accounts (MP), Enterprise WeChat (Work), Mini Programs (WxOpen), Open Platform, and WeChat Pay (TenPay V2/V3). It provides strongly-typed API wrappers for hundreds of WeChat endpoints, message/event handling with a rich class hierarchy, caching abstractions, and utilities for signature verification, encryption, and OAuth. The architecture is a modular monolith with separate packages per platform, sample MVC applications for .NET 4.5/8/10, and dependency injection support via registration modules. Key entry points include static API classes (e.g., `CommonJsonSend.Send<T>()`), message handler base classes, and container-based token management. The SDK also includes experimental components such as an MCP server for AI tool integration and a browser plugin for development assistance. The codebase demonstrates consistent patterns: base result classes with error code handling, container caching with capability flags, extension methods for payment notification decryption, and automatic access token refresh via `ApiHandlerWapper.TryCommonApi`. While the SDK is actively maintained and supports modern .NET versions, it carries some technical debt from legacy .NET 4.x support, duplicated DTOs across platforms, and incomplete test coverage that relies on live credentials. Overall, it is a functional and widely-used SDK (8900+ stars) with solid engineering practices but room for improvement in code consolidation and test automation.
Hearthstone Deck Tracker is a Windows desktop companion application for the digital card game Hearthstone. It reads the game's log files and memory (via HearthMirror) to reconstruct real-time game state, providing an in-game overlay that displays the player's deck, opponent's known cards, draw probabilities, card generation predictions, and various counters for in-game effects. It also offers deck management (import/export, editing, versioning), match history and statistics, and integration with HSReplay.net for cloud sync, replays, and premium features like mulligan guides and arena drafting assistance. The application follows a custom MVVM (Model-View-ViewModel) architecture using .NET Framework and XAML for the UI. The core game state engine is driven by log watchers and handlers that parse Hearthstone's power log, while memory reading provides additional data like the player's collection and current deck. The overlay system consists of multiple transparent windows that can be configured per game mode (Constructed, Arena, Battlegrounds, Mercenaries). A plugin system allows third-party extensions, and an auto-updater (Squirrel) handles distribution. Key entry points include the main application window (App.xaml.cs), the log watcher manager (LogWatcherManager), the scene handler that transitions between game modes, and the various overlay view models. Data flows from log files and memory into a shared game state object, which is then consumed by counters, effect trackers, and UI components. External dependencies include HearthDb (card database), HearthMirror (memory reading library), HSReplay.net APIs, and the Hearthstone game client itself. The codebase is large and actively maintained, with frequent updates to support new Hearthstone expansions and game modes. However, it carries significant technical debt: heavy use of hardcoded card IDs, brittle regex-based log parsing, a custom UI framework that diverges from standard .NET patterns, and deep coupling to game-specific mechanics. While functional and feature-rich, the architecture shows signs of organic growth rather than deliberate design, making isolated reuse of components challenging without adaptation.
This repository is the source code for **PerfView**, a performance analysis toolkit developed by Microsoft. It is a hybrid application/library primarily classified as an application, centered around a Windows desktop GUI (WPF) for visualizing trace data, but it also contains a highly reusable core library (`Microsoft.Diagnostics.Tracing.TraceEvent`) for programmatic trace processing. The system's ground truth is the analysis of system and application performance through tracing. It ingests trace data from multiple sources (Windows ETW, Linux `perf`/`strace`, .NET EventPipe, heap dumps), parses them into a unified stack trace model, resolves symbols (PDB, ELF), and provides interactive visualizations (flame graphs, call trees, heap diagrams) and automated analysis reports. The architecture is a monolith with a well-separated core library. The `TraceEvent` library is the standout component, offering a clean `StackSource` abstraction, a plugin-based automated analysis framework (`Analyzer`), and robust symbol resolution. The `FastSerialization` library is another reusable gem for efficient object graph serialization. **Critical Caveat:** The codebase uses a **non-standard C# dialect** (e.g., `Func<bool>`, `ref uint`, `where T : ArgumentException`) that is not compatible with standard .NET compilers. This represents a severe technical drift risk and a significant barrier to external contribution or reuse of individual components without substantial adaptation. The code is actively maintained by Microsoft but carries significant technical debt tied to its proprietary toolchain.
This repository is a comprehensive IoT device driver library for .NET nanoFramework. It provides bindings for hundreds of sensors, actuators, displays, and communication modules (e.g., BME280, SSD1306, NFC, Modbus, cellular modems, GPS). The architecture is a collection of independent driver projects, each with its own samples, tests, and documentation. Shared utility libraries (e.g., System.Device.Model, NumberHelper, SpanByte compatibility shims) support cross-cutting concerns. The codebase is actively maintained with frequent commits, but the sheer number of drivers (300+) leads to varying quality, some code duplication (e.g., SpanByte classes in multiple locations), and partially auto-generated code. Networking components like DHCP server, DNS server, and Home Assistant MQTT integration extend the library beyond raw sensor access. The primary use case is building embedded IoT applications on microcontrollers (ESP32, STM32) running nanoFramework.
PECmd is a command-line tool for parsing Windows prefetch (.pf) files. It processes single files or directories, outputs detailed information in console, JSON, CSV, or HTML formats, and supports features like Volume Shadow Copy processing and deduplication. The application is built with .NET using System.CommandLine for argument parsing, Serilog for logging, and the Prefetch library for core parsing logic. All logic resides in Program.cs, which handles argument processing, file enumeration, prefetch parsing, and output generation. The tool is actively maintained with recent commits and up-to-date dependencies, targeting both .NET Framework 4.7.2 and .NET 9.0 for broad compatibility.
RetroMultiTools is a cross-platform desktop application built with Avalonia (.NET 8) that serves as a comprehensive utility suite for retro gaming enthusiasts. It provides a unified interface for ROM management, including browsing, inspection, patching (IPS/BPS/xDelta), format conversion (N64 byte order, CHD, archive extraction), verification (CRC, MD5, SHA, DAT file validation, dump quality checks), and emulator configuration for RetroArch, MAME, Mednafen, and Analogue consoles. The application also features a gamepad key mapper, disc burning and USB imaging tools, cheat code conversion across 23 systems, remote file transfer (FTP, SFTP, WebDAV, S3, cloud storage), and a self-updater. It supports 20 languages and runs on Windows, Linux, macOS, and FreeBSD, with Flatpak packaging available. The architecture is a monolithic desktop application with a sidebar navigation tree that loads over 40 distinct views, each backed by a code-behind file and often a static utility class. The core pattern is event-driven UI with async operations using IProgress<string> and CancellationToken for long-running tasks. Localization is handled via a singleton LocalizationManager that binds to XAML controls. Settings are persisted as JSON via AppSettings. The application integrates with external tools (chdman, DolphinTool, cdrecord, dd) and libraries (SDL2, SharpCompress, FluentFTP, SSH.NET, AWS SDK) for platform-specific functionality. Key strengths include a consistent async progress pattern across all tools, reusable utility classes for file operations, path validation, and drag-and-drop, and deep format knowledge for retro gaming file formats. The codebase demonstrates solid engineering practices for a desktop utility, though it suffers from some monolithic view files and hardcoded data that could benefit from modularization. No unit tests are visible, and the large feature surface introduces maintenance overhead.
Watt Toolkit (Steam++) is a cross-platform desktop application that serves as a multi-functional game toolbox primarily for Steam users. The system provides network acceleration via a local reverse proxy (YARP-based) with HTTPS interception, DNS analysis, and multiple proxy modes (Hosts, System, PAC, VPN, DNS intercept). It includes plugins for Steam account switching, two-factor authenticator management (import/export/recovery), game library management, ArchiSteamFarm integration for card farming, and game tools. The architecture is a modular plugin system built with Avalonia UI, .NET, and ReactiveUI, using a multi-process IPC model for privilege separation. External dependencies include WinDivert for Windows packet interception, XunYou SDK for game acceleration, and ArchiSteamFarm for automated Steam actions. The codebase demonstrates a complex but functional architecture with significant platform-specific code and some areas of technical debt.
SnapX is a cross-platform screenshot and screen recording tool, forked from ShareX, with extensive upload capabilities to dozens of services (image hosts, file storage, pastebins, URL shorteners). It features image effects (adjustments, filters, manipulations), OCR via PaddleOCR, QR code generation/scanning, hotkey automation, and clipboard monitoring. The application is built with Avalonia UI and .NET 10, targeting Linux, Windows, macOS, and FreeBSD. It includes a CLI, a native messaging host for browser integration, and a comprehensive settings system. The codebase is in early access with many features ported from ShareX but several stubs and incomplete implementations remain, particularly in screen recording, image annotation, and some uploaders. The architecture follows a core library (SnapX.Core) with separate UI (SnapX.Avalonia) and CLI projects, using MVVM pattern and dependency injection. While functional, the project exhibits significant technical debt and incomplete feature parity with its predecessor.
OptimaJet.Workflow is a .NET workflow engine library designed for business process management and automation. It provides a core runtime for defining, executing, and persisting workflow schemes (process definitions) across multiple database backends including SQL Server, MySQL, PostgreSQL, Oracle, SQLite, and MongoDB. The engine supports multi-tenancy, version control of workflow schemes, and includes a visual HTML5 designer for creating workflows. It is architected as a library/framework layer, intended to be integrated into applications rather than running as a standalone service. The codebase demonstrates a hybrid architecture, combining modern .NET Core samples with legacy .NET Framework implementations using Windows Workflow Foundation (WWF). This duality is evident in the presence of both `OptimaJet.Workflow.Core` (modern) and `Other/WorkflowFoundation` (legacy) directories. The library relies heavily on the Provider Pattern for persistence, allowing developers to swap database backends via dependency injection. It also features a robust migration framework (FluentMigrator for SQL, custom scripts for MongoDB) to manage schema evolution, particularly around multi-tenancy support (`TenantId` columns). While the library offers solid engineering patterns like generic database abstraction (`DbObject<T>`) and async/await persistence, the codebase suffers from significant technical drift. It includes deprecated technologies such as `System.Workflow` and WCF, and sample applications rely on older versions of frameworks like ABP (v6.5.0) and .NET Core 2.2. The duplication of persistence logic across five different database providers increases maintenance overhead and the risk of schema drift between implementations.
Elib2Ebook is a .NET 10 application that downloads books from 60+ online libraries (Litres, MyBook, BookRiver, etc.) and converts them into standard ebook formats (EPUB, FB2, CBZ, JSON, TXT). It is a dual-deployment solution: a CLI tool and a Blazor web UI, both sharing a core domain and service layer. The architecture is a layered .NET solution with Domain, DomainServices, and per-site ExternalServices projects, using a reflection-based GetterFactory to auto-discover site adapters. The system handles site-specific anti-bot measures, authentication, and pagination, then normalizes content into a common domain model before passing it to format-specific builders.
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).
VoicemeeterFancyOSD is a Windows desktop application that provides a customizable on-screen display (OSD) for the Voicemeeter virtual audio mixer. It overlays real-time audio parameter changes (gain, mute, solo, bus assignments, etc.) on top of fullscreen applications without hooking into graphics APIs, using a combination of WPF, native WinAPI calls, and a custom DXGI bridge DLL. The application runs as a system tray icon and continuously polls the Voicemeeter Remote API to detect parameter changes, then displays animated OSD strips that mimic Voicemeeter's own UI style. It supports multiple Voicemeeter versions (Standard, Banana, Potato) and offers extensive configuration via an INI file and a settings window. The architecture is a hybrid .NET WPF application with a native C++ host and bridge. The main .NET assembly (VoicemeeterOsdProgram) handles UI, configuration, Voicemeeter API communication, and update management. A separate native host (VoicemeeterFancyOsdHost) loads the .NET runtime and hosts the WPF window, while a DXGI.dll bridge intercepts DirectX calls to achieve true topmost overlay behavior. Key entry points include Program.cs (application startup), App.xaml.cs (initialization), OsdWindowManager (OSD lifecycle), VoicemeeterApiClient (API polling), and BandWindow (custom topmost window). The application relies on several NuGet packages (ini-parser, WpfScreenHelper, Hardcodet.NotifyIcon, a-tg.VmrapiDynWrapExt) and internal WinAPI functions. The codebase demonstrates solid engineering practices with MVVM separation, custom reusable controls, and a modular structure. However, it suffers from maintenance risks due to its reliance on undocumented WinAPI, a fragile host process trick (renamed ApplicationFrameHost.exe), and a preview .NET version. There are no automated tests or CI pipelines, and the repository shows no recent commits, indicating a stale maintenance state. Despite these issues, several components (e.g., BandWindow, OptionsBase, Logger) are well-crafted and could be extracted for reuse in other Windows desktop applications.
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.
Yi.Abp.Admin is a full-stack enterprise administration framework built on ASP.NET Core (ABP vNext framework) with multiple Vue 3 frontends (Pure Admin, Vben5, RuoYi, and a BBS variant). It provides RBAC, multi-tenancy, audit logging, setting management, code generation, and OAuth support (QQ, Gitee). The backend follows Domain-Driven Design with modules like Yi.Framework.Rbac and Yi.Framework.TenantManagement, using SqlSugar ORM as a replacement for ABP's default EF Core. The frontends feature dynamic route generation from backend permissions, reusable UI components (dialog, cropper, table bar, form API), and state management with Pinia. The monorepo also includes a CLI tool for scaffolding new modules. Despite some duplication across frontends and ABP customizations that may cause upgrade friction, the codebase demonstrates solid engineering with well-separated concerns and several independently usable components.
This is the official Microsoft .NET documentation repository, containing conceptual articles, tutorials, and thousands of compilable code snippets. It is not a software application, data pipeline, or research project. The primary purpose is to document .NET APIs, frameworks, and best practices through markdown and illustrative C# (and some VB, F#, C++) examples. The code snippets demonstrate realistic usage of .NET libraries, Azure SDKs, Orleans, AI/ML extensions, and more, but are designed for education and reference, not production deployment. The repository is actively maintained with frequent commits, automated build verification, and strict quality controls (markdown linting, link checking, snippet compilation). While the snippets themselves vary in modernity and some legacy examples exist, the overall drift is low because updates keep pace with .NET releases. Reusable components are limited to isolated patterns (custom JSON converters, middleware pipelines, testing utilities) that could be extracted, but most code is tightly coupled to the documentation context.
DuplexSpyCS is a full-featured Remote Access Trojan (RAT) command-and-control (C2) framework written in C# (.NET WinForms). It consists of a server-side management console and multiple payload variants (winClient48, winClient48DLL, Tipoff, etc.) that provide comprehensive post-exploitation capabilities: file manager, remote desktop, keylogger, webcam/microphone streaming, registry editor, process/task manager, remote shell (including xterm via WebView2), SOCKS5 proxy, and a plugin system for credential theft (Chrome, Edge, Firefox, MobaXterm). Communication uses a custom binary protocol (clsDSP) over TCP, TLS, or HTTP with RSA-AES hybrid encryption. The payloads employ persistence via registry/startup, UAC bypass, process injection (APC, EarlyBird, CreateRemoteThread, etc.), and fileless execution. The codebase is extensive but exhibits significant code duplication across payload projects, many incomplete or stub features, and outdated dependencies (AForge, NAudio, SharpPcap). It is explicitly designed for offensive security research and learning, but carries high risk of misuse.
Diffusion Toolkit is a WPF desktop application for organizing, searching, and browsing AI-generated images. It scans folders for images, extracts generation parameters (prompt, seed, model, CFG, workflow, etc.) from multiple formats (AUTOMATIC1111, ComfyUI, NovelAI, etc.), and stores them in a SQLite database for fast metadata search, filtering, and album management. The application provides a rich thumbnail grid, preview pane, folder/album/tag navigation, and supports videos, external applications integration, and auto‑updating via GitHub releases. Although it demonstrates a depth of domain knowledge and addresses a real need for AI artists, the codebase has notable architectural anti‑patterns (global static service locator, monolithic classes, raw SQL in migrations, large XAML files), is tied to Windows/WPF with no headless component, and uses a forked version of sqlite‑net. The code is actively maintained with frequent commits, but its reusability is limited by tight coupling and lack of an inversion of control container.
NCalc is a .NET library for parsing and evaluating mathematical expressions, written in C# and targeting .NET Framework 3.5. It uses ANTLR 3.3 to generate a lexer and parser from a custom grammar, producing an abstract syntax tree (AST) of logical expressions. The library supports arithmetic, logical, bitwise, comparison, and ternary operators, as well as built-in functions (Abs, Sin, Round, etc.) and user-defined functions and parameters via event handlers. It also includes expression caching, error detection, and serialization. The codebase is well-structured for its era, with a clear separation between grammar, domain model, and evaluation logic. However, it is explicitly unmaintained and superseded by a newer version (ncalc/ncalc). The project uses outdated dependencies (ANTLR 3.3, .NET 3.5) and includes binary DLLs, making it unsuitable for modern .NET projects without significant migration effort. The primary value is as a historical reference or for understanding expression evaluator design patterns.
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.
This repository previously hosted the dotnet/format tool, a code formatter for .NET projects. However, as indicated by the README, development and issue tracking have been consolidated into the dotnet/sdk repository. The repository now contains only Git metadata and a configuration file disabling Dependabot updates. No source code, build scripts, or documentation beyond the redirect notice are present. The repository is effectively archived and should not be used for any new work. Users seeking the dotnet/format tool should refer to the dotnet/sdk repository.