vswhere is a command-line utility developed by Microsoft to locate installed instances of Visual Studio and related products (Build Tools, etc.). It queries the Visual Studio Setup Configuration API (ISetupConfiguration) and the Windows Registry to discover installation paths, versions, and workloads. The tool supports filtering by version range, product ID, workload requirements, and legacy installations. Output can be formatted as text, JSON, XML, or raw values, making it suitable for build scripts and deployment automation. The architecture consists of a core static library (vswhere.lib) containing the logic for parsing, querying, and formatting, linked against a minimal executable entry point (vswhere.exe). It relies on COM interfaces for setup configuration and standard C++17 libraries for string and filesystem operations.
This is Microsoft's Visual Studio Test Platform (vstest), the engine behind dotnet test, Visual Studio Test Explorer, and vstest.console. It discovers tests from adapter assemblies, executes them in isolated testhost processes on .NET Framework and .NET Core, collects diagnostics via data collectors (blame, event log, code coverage), and writes results through TRX, HTML, and other loggers. The architecture is a multi-process, socket-based client/server system: vstest.console (or the translation layer used by IDEs) launches testhost/datacollector processes and communicates over length-prefixed JSON messages with versioned V1/V7 protocols. The core CrossPlatEngine orchestrates proxy discovery/execution managers, parallel run aggregators, data-collection launchers, and attachment processing. Key entry points are src/vstest.console/Program.cs, src/testhost/Program.cs, src/datacollector/DataCollectorMain.cs, and the Microsoft.TestPlatform.VsTestConsole.TranslationLayer API. Microsoft.TestPlatform.ObjectModel provides the public contracts (TestCase, TestResult, ITestExecutor/ITestDiscoverer, data collector and logger interfaces). Microsoft.TestPlatform.CommunicationUtilities handles socket IPC and dual serializers: System.Text.Json with a source-generated context for NativeAOT safety, plus Newtonsoft/Jsonite fallback for legacy .NET Framework paths. Microsoft.TestPlatform.Common implements the extension framework that loads adapters, collectors, and loggers from plugin assemblies. Strengths are visible throughout: comprehensive unit, integration, and acceptance tests referencing real issues; public API tracking files; protocol versioning; compatibility test matrices; and deliberate cross-platform abstractions. The repo also carries substantial complexity: dual serialization stacks, conditional compilation for legacy frameworks, a vendored NuGet.Frameworks clone, and many InternalsVisibleTo bridges. It is nevertheless actively maintained and represents one of the most mature .NET test execution infrastructures available.
A Visual Studio extension (VSIX) that integrates SonarQube/SonarCloud static analysis into the IDE. It provides real-time code quality and security analysis for C#, VB.NET, C/C++, JavaScript/TypeScript, CSS, and other languages via an embedded SLCore backend (Java process) and a separate Roslyn analyzer server for .NET. The extension supports both standalone analysis and 'connected mode' that binds to SonarQube/SonarCloud servers, including project binding, credential management, issue visualization with flows and locations, security hotspots, taint vulnerabilities, dependency risks, quick fixes, rule education (HTML-to-XAML rendering), and telemetry. The architecture is modular, heavily relying on MEF for dependency injection, with distinct assemblies for core abstractions, VS integration, connected mode UI, issue visualization, security-specific features, and education. The codebase is well-tested with extensive unit tests and some integration tests, but shows signs of ongoing migration from legacy binding models to a modern SLCore-based protocol, resulting in some technical debt and backward-compatibility code.
This repository is the official vcpkg registry, a collection of build recipes (ports) for over 2000 C/C++ libraries, managed by Microsoft. It is not the vcpkg tool itself but the package database that the tool consumes. The primary purpose is to define how each library is downloaded, patched, built, and installed across multiple platforms (Windows, Linux, macOS, Android, etc.) using CMake and other build systems. The architecture is a flat directory of port definitions, each containing a `vcpkg.json` metadata file and a `portfile.cmake` build script, along with patches and CMake config templates. The registry also includes a version database (`versions/`) for baseline and versioning resolution, CI test ports, and helper scripts for tool acquisition and deployment. While the codebase is well-organized and follows consistent patterns, it is primarily a data repository of package definitions rather than a reusable software library. The vcpkg tool itself is maintained in a separate repository.
GENie is a build system generator that creates native project files (Makefile, Visual Studio, Xcode, Ninja, etc.) from Lua-based project descriptions. It embeds Lua 5.3.0 as its scripting engine and uses a hierarchical configuration system (solution/project/platform/configuration) to manage build settings. The tool processes user-defined Lua scripts (typically premake4.lua) to generate tool-specific build files through registered actions. Architecture consists of a C host layer handling platform abstractions, Lua modules for core functionality (solution/project/config management, action/option system), toolchain-specific compilers/linkers, and generator actions for each build system. Key entry points are src/host/premake_main.c (main) and the embedded Lua API. Data flow involves: CLI args → Lua state initialization → user script execution → action-specific file generation. External dependencies are limited to system libc and platform APIs; Lua is fully embedded.
UEFI:NTFS is a UEFI bootloader application that enables booting from NTFS or exFAT partitions on UEFI systems lacking native drivers for these filesystems. It is primarily designed for use with Rufus to create bootable USB drives with Windows installation media or Windows To Go. The bootloader loads a filesystem driver (NTFS or exFAT), mounts the target partition, and chain-loads the standard UEFI bootloader from that partition. The source code is clean, well-commented, and demonstrates careful handling of UEFI firmware quirks, such as driver conflicts and Secure Boot validation. The project compiles with either gnu-efi or EDK2, supports multiple architectures (x86, x64, ARM, ARM64, RISC-V, LoongArch), and includes Visual Studio and GCC build configurations with CI pipelines. While the code is not reusable outside of UEFI development, it serves as a high-quality reference for writing UEFI applications and chain-loaders.
This repository is an awesome list of Visual Studio Code extensions and resources, with the README.md serving as the primary product. It does not contain a runnable application but functions as a curated reference guide for developers seeking VS Code extensions. The repository includes a GitHub Actions workflow (links.yml) that automatically validates all links in the README using the awesome_bot tool to prevent link rot. Contributions are governed by strict guidelines ensuring consistent formatting, alphabetical ordering, and inclusion of screenshots/GIFs where possible. While the core content is static, the CI pipeline demonstrates a reusable pattern for documentation maintenance in open-source projects.