Wails is a Go framework for building cross-platform desktop applications using web frontends (HTML/CSS/JS). It provides a CLI tool for project scaffolding, development server, and building. The architecture consists of a Go backend that communicates with an embedded WebView via a binding system that auto-generates TypeScript/JavaScript wrappers for Go services. It supports Windows (WebView2), macOS (WebKit), Linux (GTK/WebKit), and mobile (iOS/Android). Key entry points include `application.New()` in v3 and `wails.Run()` in v2. External dependencies include the WebView2 runtime on Windows, WebKitGTK on Linux, Cocoa on macOS, and various system libraries. The repository contains both v2 (legacy) and v3 (current) versions, with v3 introducing a new binding generator, built-in task runner (`wake`), improved service lifecycle, and cross-platform scaffolding.
Microsoft PowerToys is a modular suite of Windows productivity utilities designed to enhance the user experience for power users. The codebase is a large, multi-language monolith (C++, C#, WinUI 3, WPF) organized around a central runner process that loads modules (e.g., FancyZones, PowerToys Run, Image Resizer, Advanced Paste, Peek, Workspaces) as dynamic libraries or COM objects. Each module has its own settings, telemetry, UI, and IPC pipeline. The architecture relies heavily on Win32 APIs, COM interop, named pipes, and ETW tracing. Key entry points include the runner executable, the Settings UI (WinUI 3), and per-module interfaces like `AdvancedPaste` or `PowerRename`. The repository is actively maintained by Microsoft with frequent commits and a large community, but the sheer number of modules introduces code duplication, mixed UI frameworks, and some technical drift.
QTTabBar is a Windows Explorer shell extension that adds tabbed browsing, customizable toolbars, and a plugin system to File Explorer. It integrates as a COM band object (IDeskBand) into Explorer's rebar, providing features such as tab management, mouse gestures, keyboard shortcuts, folder groups, and a button bar. The architecture is a hybrid of WinForms and WPF, with heavy use of COM interop and native API hooking via the MinHook library. Key entry points include the BandObject base class, the QTCommandBar band, and the PluginServer that loads interactive and background plugins. External dependencies include the .NET Framework 4.8, Windows Shell APIs, and a native C++ hook library (QTHookLib). The system persists configuration in the Windows Registry and supports multi-language localization. While the codebase is mature and feature-rich, it exhibits technical drift due to reliance on legacy .NET Framework, extensive COM interop that may break on newer Windows versions, and some deprecated APIs. The plugin system and several utility components (e.g., PropVariant wrapper, ChineseCalendar) are well-crafted and potentially reusable in other projects.
WinFormsComInterop is a .NET library that provides a custom ComWrappers implementation for Windows Forms (and WebView2) to enable NativeAOT compilation and trimming. It includes a source generator that automatically produces Runtime Callable Wrappers (RCW) and COM Callable Wrappers (CCW) for arbitrary COM interfaces, reducing manual interop code. The repository also contains facade assemblies that stub out dependencies on System.Windows.Forms, WindowsBase, PresentationCore, and Microsoft.Web.WebView2.Core, allowing AOT-friendly builds without full desktop framework references. Multiple sample applications demonstrate usage with WinForms, Blazor Hybrid, hosted WinForms in native DLLs, and trimming. The project is actively maintained and targets .NET 6 through .NET 10, but relies on pre-release SDK versions and has some experimental components (WPF, WinUI) that are not production-ready.
FastCopy (published as RoboCopyEx, v1.2.1.0) is a Windows desktop utility that replaces Explorer's default copy/move/paste/delete with a robocopy-backed engine. In production it is three cooperating native components: a WinUI 3 (C++/WinRT, Windows App SDK 1.8) application that renders copy progress, a speed graph, pause/resume, duplicate-file conflict resolution and delete confirmations; a COM shell-extension DLL that adds copy/move/paste/delete items to both the new Windows 11 and legacy Explorer context menus; and a global keyboard-hook executable that intercepts Ctrl+V inside Explorer to route pastes through FastCopy. A fastcopy:// URI handler (CommandLineHandler) is the transport by which components pass operations to the main app. The solution is an MSIX package of six projects: FastCopy (UI), FastCopyShellExtension (Explorer COM DLL), FastCopyKeyboardHook (global hook EXE), RobocopyInjection (DLL injected into robocopy.exe to expose per-file progress), UnitTest, and SpeedTest — a TUI benchmark that empirically compares robocopy, xcopy, std::filesystem, IFileOperation and SHFileOperation. The central data flow: RobocopyViewModel builds robocopy arguments; RobocopyProcess launches robocopy.exe suspended inside a JobObject, injects a DLL to force English locale output, then streams the child's stdout through a regex-driven template parser (OutputRegexParseBase) while ProcessIOUpdater samples GetProcessIoCounters/GetSystemTimes to animate the Win2D speed graph, taskbar progress and Windows toasts. Settings are persisted via a WinRT IPropertySet-backed Settings class and MVVM runtime classes declared in IDL. Engineering quality is mixed and should be read from the code rather than the README's speed claims. The repo knowingly ships a crash after the window is closed; RobocopyInjectDll.h and CreateSuspend.h contain null-byte encoding corruption; numerous features are disabled ('Under development!') or commented out; and the app depends on a third-party WinUI3Package (essential:) control library plus dual vcpkg/NuGet dependency chains, making rebuilds fragile outside the author's machine. The DLL-injection and global-hook design is also the likely reason the Store rejected the package, per drama.md. The last commit (2026-09-19) indicates the project is still actively developed. Despite containing a benchmark harness and careful README performance tables, this is an application, not a data/research repository: there are no datasets, notebooks, or pipelines, and the SpeedTest project is an empirically driven engineering tool, not analysis. Its most durable artifacts are the independently extractable OS-interop helpers and parsing templates described below.