# MSVC Microsoft's C++, C, and assembly development tools and libraries available with Visual Studio on Windows. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## C++ in the Age of AI: Visual Studio at CppCon 2026 DevFeed: [C++ in the Age of AI: Visual Studio at CppCon 2026]() Original publisher: [Read original article]() Author: Augustin Popa Published: 2026-09-14T19:34:43Z Content type: article Language: en Sources: [C++ Team Blog]() Topics: [C++](), [Visual Studio](), [GitHub Copilot](), [Visual Studio 2026](), [build performance](), [MSVC](), [debugging](), [Optimization](), [Refactoring](), [Artificial Intelligence]() Tags: [ai](), [build-optimization](), [build-performance](), [c-plus-plus](), [copilot](), [cppcon](), [debugging](), [github-copilot](), [msvc](), [visual-studio](), [visual-studio-2026]() ### AI overview This companion reading guide covers how Visual Studio 2026 is evolving C++ development with improved code navigation, build and runtime performance, language feature support, debugging, modernization, refactoring, and AI-assisted workflows using GitHub Copilot. ### Source excerpt At CppCon 2026, we shared how Visual Studio is evolving to help you work more effectively with large C++ codebases, improve build and runtime performance, adopt the latest language features, and incorporate AI into your existing workflows. This post is a companion reading guide for our session, C++ in the Age of AI: How Visual [...] The post C++ in the Age of AI: Visual Studio at CppCon 2026 appeared first on C++ Team Blog. ## What's New for C++ Developers in Visual Studio 2026 (18.7 - 18.10) DevFeed: [What's New for C++ Developers in Visual Studio 2026 (18.7 - 18.10)]() Original publisher: [Read original article]() Author: Augustin Popa Published: 2026-09-14T06:38:16Z Content type: article Language: en Sources: [C++ Team Blog]() Topics: [Visual Studio 2026](), [C++](), [GitHub Copilot](), [MSVC](), [AI-assisted coding](), [CMake](), [Git](), [Submodules]() Tags: [2026](), [build-optimization](), [c-plus-plus](), [cmake](), [copilot](), [git](), [modernization](), [msvc](), [submodules](), [testing](), [tools](), [visual-studio](), [visual-studio-2026]() ### AI overview This Microsoft C++ Team Blog post recaps Visual Studio 2026 versions 18.7 through 18.10 for C++ developers. It covers C++ reliability fixes, GitHub Copilot modernization for upgrading MSBuild and CMake projects to newer MSVC Build Tools, improved code navigation, discoverable MSVC Build Tools installations, Git worktrees and submodules in the IDE, and debugging improvements. ### Source excerpt Over the past few months, we have continued shipping monthly Visual Studio 2026 releases, delivering improvements across all stages of the development cycle. In this blog post, we'll recap everything that changed from version 18.7 through 18.10 (released this month) that is relevant for C++ developers. This includes new tools for maintaining and navigating C++ [...] The post What's New for C++ Developers in Visual Studio 2026 (18.7 - 18.10) appeared first on C++ Team Blog. ## Microsoft at CppCon 2026 DevFeed: [Microsoft at CppCon 2026]() Original publisher: [Read original article]() Author: Augustin Popa Published: 2026-09-14T00:16:42Z Content type: news Language: en Sources: [C++ Team Blog]() Topics: [C++](), [Microsoft](), [Visual Studio](), [Visual Studio 2026](), [GitHub Copilot](), [MSVC](), [Visual Studio Code](), [Artificial Intelligence](), [Optimization](), [CMake]() Tags: [ai](), [c-plus-plus](), [cmake](), [copilot](), [cppcon](), [github-copilot](), [microsoft](), [msvc](), [optimization](), [safety](), [survey](), [visual-studio](), [visual-studio-2026]() ### AI overview Microsoft's CppCon 2026 sessions cover modern C++ development, including AI-assisted workflows, MSVC, Visual Studio, Visual Studio Code, compiler optimization, C++ safety, and stricter compiler warnings. The article also provides conference logistics, speaker sessions, and a survey invitation. ### Source excerpt Microsoft will be at CppCon 2026 in Aurora, Colorado, which is taking place from September 14 through 18. Join us for talks from Microsoft speakers and colleagues across the C++ community and visit the Microsoft booth Monday through Thursday to meet the team and discuss the tools, technologies, and challenges that matter to you. If [...] The post Microsoft at CppCon 2026 appeared first on C++ Team Blog. ## MSVC C++23: constexpr cmath with LLVM Libc DevFeed: [MSVC C++23: constexpr cmath with LLVM Libc]() Original publisher: [Read original article]() Author: Cody Miller Published: 2026-09-10T21:19:59Z Content type: article Language: en Sources: [C++ Team Blog]() Topics: [MSVC](), [C++](), [math]() Tags: [c-plus-plus](), [feature](), [llvm](), [math](), [msvc](), [os](), [performance](), [tools](), [visual-studio]() ### AI overview MSVC is preparing an experimental C++23 implementation of compile-time-evaluable standard math functions, powered by a new math library. The article explains the existing UCRT math-function arrangement and concerns about accuracy, compatibility, performance, and OS-dependent behavior. ### Source excerpt Proposal P0533R9 made numerous math functions in the standard library compile-time evaluable in C++23. Implementing the feature required a good bit of time and effort, but MSVC is preparing its experimental implementation for the 14.52 build tools (compiler version 19.52)! We are still refining the feature, so expect the dust to settle only when this [...] The post MSVC C++23: constexpr cmath with LLVM Libc appeared first on C++ Team Blog. ## MSVC Build Tools Preview updates - August 2026 DevFeed: [MSVC Build Tools Preview updates - August 2026]() Original publisher: [Read original article]() Author: Eric Brumer Published: 2026-08-13T15:01:10Z Content type: article Language: en Sources: [C++ Team Blog]() Topics: [MSVC](), [C++](), [Compiler](), [toolchain](), [Code generation](), [Optimization](), [Visual Studio]() Tags: [c-plus-plus](), [code-generation](), [diagnostics](), [features](), [ide](), [msvc](), [optimization](), [release](), [tools](), [updates](), [visual-studio](), [visual-studio-2026]() ### AI overview The article summarizes August 2026 updates to the MSVC Build Tools Preview, targeting the v14.52 release. It covers compiler conformance, diagnostics, C++ modules, code generation, optimization, and ARM64 improvements. ### Source excerpt Try the latest updates to MSVC Build Tools Preview The post MSVC Build Tools Preview updates - August 2026 appeared first on C++ Team Blog. ## C++ Dependencies Without the Headache: vcpkg + Copilot CLI DevFeed: [C++ Dependencies Without the Headache: vcpkg + Copilot CLI]() Original publisher: [Read original article]() Author: Augustin Popa Published: 2026-07-20T21:05:25Z Content type: article Language: en Sources: [C++ Team Blog]() Topics: [GitHub Copilot CLI](), [Vcpkg](), [C++](), [GitHub Copilot](), [MSVC](), [Command-line interface](), [GitHub]() Tags: [blog](), [c-plus-plus](), [cli](), [cmake](), [copilot](), [github](), [github-copilot](), [github-copilot-cli](), [msvc](), [open-source](), [programming](), [pure-virtual-c-plus-plus](), [vcpkg](), [writing-code]() ### AI overview A practical walkthrough of building a C++ console application from an empty folder with CMake, MSVC Build Tools, vcpkg, and GitHub Copilot CLI. It demonstrates dependency selection, installation, integration, reproducible builds, and controlled dependency updates through a terminal-first workflow. ### Source excerpt At Pure Virtual C++ 2026, we build a C++ console app from an empty folder using CMake, MSVC, and GitHub Copilot CLI. This walkthrough shows a practical prompt sequence for dependency selection, reproducible builds, and controlled updates. The post C++ Dependencies Without the Headache: vcpkg + Copilot CLI appeared first on C++ Team Blog. ## Pure Virtual C++ 2026 Is Tomorrow and On-Demand Sessions Are Now Available DevFeed: [Pure Virtual C++ 2026 Is Tomorrow and On-Demand Sessions Are Now Available]() Original publisher: [Read original article]() Author: Marian Luparu Published: 2026-07-20T16:05:54Z Content type: news Language: en Sources: [C++ Team Blog]() Topics: [C++](), [MSVC](), [Optimization](), [Vcpkg](), [GitHub Copilot CLI]() Tags: [announcement](), [blog](), [c-plus-plus](), [cpu](), [msvc](), [optimization](), [performance](), [pure-virtual-c-plus-plus](), [release](), [synthetic](), [twitch](), [youtube]() ### AI overview Pure Virtual C++ 2026 is a free virtual conference whose on-demand sessions are already available on YouTube. The article previews the live broadcast and highlights sessions on Sample Profile-Guided Optimization, C++ tooling, package management, MSVC, and C++ standards. ### Source excerpt The on-demand sessions for Pure Virtual C++ 2026 are available now on YouTube. Watch seven talks on SPGO, vcpkg + Copilot CLI, CMake Tools, PackageReference, MSVC upgrades, and C++23/26 status -- then join us live tomorrow. The post Pure Virtual C++ 2026 Is Tomorrow and On-Demand Sessions Are Now Available appeared first on C++ Team Blog. ## Bit-field layout DevFeed: [Bit-field layout]() Original publisher: [Read original article]() Published: 2026-02-22T08:00:00Z Content type: tutorial Language: en Sources: [MaskRay]() Topics: [implementation](), [C](), [C++](), [Compiler](), [clang](), [gcc](), [LLVM](), [MSVC]() Tags: [c](), [c-plus-plus](), [clang](), [codegen](), [compiler](), [compiler-optimization](), [gcc](), [implementation](), [llvm](), [msvc]() ### AI overview This article explains how C and C++ bit-field layout is implementation-defined and governed primarily by platform ABIs. It distinguishes ABI-defined storage layout from compiler code generation, focusing on the Itanium ABI and describing differences in the Microsoft ABI. ### Source excerpt The C and C++ standards leave nearly every detail to the implementation. C23 §6.7.3.2: An implementation may allocate any addressable storage unit large enough to hold a bit-field. If enough space remains, a bit-field that immediately follows another bit-field in a structure shall be packed into adjacent bits of the same unit. If insufficient space remains, whether a bit-field that does not fit is put into the next unit or overlaps adjacent units is implementation-defined. The order of allocation of bit-fields within a unit (high-order to low-order or low-order to high-order) is implementation-defined. The alignment of the addressable storage unit is unspecified C++ is also terse -- [class.bit]p1: Allocation of bit-fields within a class object is implementation-defined. Alignment of bit-fields is implementation-defined. Bit-fields are packed into some addressable allocation unit. ## Progress update: fixing the ReactOS test suite DevFeed: [Progress update: fixing the ReactOS test suite]() Original publisher: [Read original article]() Published: 2025-11-04T00:00:00Z Content type: opinion Language: en Sources: [Front Page on ReactOS Website]() Topics: [Testing](), [WINE](), [Windows](), [gcc](), [MSVC](), [x86]() Tags: [changes](), [developer](), [free](), [gcc](), [msvc](), [open-source](), [os](), [react](), [reactos](), [tests](), [update](), [win32](), [winapi](), [windows](), [wine](), [x86]() ### AI overview A ReactOS project developer describes work to clean up the neglected test suite. The update reports fixes to 55 existing test modules, five new modules, broader testing across Windows versions and compiler toolchains, and changes intended to improve synchronization with Wine 10.0. The supplied text also states that the full test suite can now run on Windows Vista without a bugcheck. ### Source excerpt For many years, the ReactOS test suite was neglected. It was a random collection of our own tests and old Wine tests that were only checked against Windows Server 2003 and sometimes a random newer version of Windows up to the discretion of the contributor. The Wine tests we imported were heavily modified and the changes made weren't always well documented. I'm here to clean up this mess. I have been deeply involved with the ReactOS project since 2023 and in May of 2024 I became an official project developer. ## Node.js 24.0.0 (Current) DevFeed: [Node.js 24.0.0 (Current)]() Original publisher: [Read original article]() Published: 2025-05-06T14:31:35Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [npm](), [V8](), [MSVC](), [HTTP](), [Mocha](), [Security]() Tags: [cross-platform](), [http](), [javascript](), [latest-release](), [msvc](), [node-js](), [npm](), [open-source](), [performance](), [release](), [security](), [tests](), [updates](), [windows]() ### AI overview Node.js 24.0.0 is a Current release that upgrades V8 to 13.6 and npm to 11, removes MSVC support on Windows in favor of ClangCL, improves asynchronous context tracking, expands the Permission Model, enhances the test runner, and updates Undici. It is scheduled to enter long-term support in October. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Newsletter 103 - Late 2023 news DevFeed: [Newsletter 103 - Late 2023 news]() Original publisher: [Read original article]() Published: 2023-11-05T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [debug](), [Kernel](), [gcc](), [MSVC](), [Pull Request]() Tags: [bugfixes](), [bugs](), [debug](), [debugger](), [free](), [gcc](), [msvc](), [open-source](), [os](), [react](), [reactos](), [release](), [version](), [win32](), [winapi]() ### AI overview ReactOS Newsletter 103 reports that version 0.4.15 is still planned but delayed by unresolved regressions and bugs, including a large-file copying regression. It also discusses an overhaul of the ReactOS kernel debugging setup and the use of GCC, MSVC, and WinDbg. ### Source excerpt Salutations from the ReactOS project team! In previous posts, we talked about the ReactOS releasing process and the development status of the project, as well as the hiring of our long-term developer Hermès Bélusca-Maïto (HBelusca). We are making an effort to publish at least 3 newsletters per year, depending on how the development workflow goes. In this newsletter we will highlight some of the contributions made by project developers and contributors, as well as future plans and headlines. ## What's a vtable? What's an IUnknown? DevFeed: [What's a vtable? What's an IUnknown?]() Original publisher: [Read original article]() Author: Tim Misiak Published: 2022-12-18T15:30:09Z Content type: tutorial Language: en Sources: [TimDbg]() Topics: [C++](), [Windows](), [debug](), [MSVC](), [Polymorphism]() Tags: [c-plus-plus](), [class](), [compiler](), [debugger](), [function](), [msvc](), [virtual](), [windows]() ### AI overview This tutorial explains how C++ virtual function tables, or vtables, support dynamic dispatch and how they relate to COM objects on Windows. It also introduces debugger-based techniques for examining vtables and discusses errors that can be difficult to diagnose. ### Source excerpt Understanding vtables (also called VMT/Virtual Method Tables or VFT/Virtual Function Tables) is important for understanding how many C++ features work on any OS. They are even more important to understand on Windows, where vtables are used for communication between modules using COM. There are a few types of errors that can happen when things go wrong with them, and some of these will be extremely difficult to diagnose unless you understand how vtables actually work. ## Debugger Lies: Stack Corruption DevFeed: [Debugger Lies: Stack Corruption]() Original publisher: [Read original article]() Author: Tim Misiak Published: 2022-08-21T16:57:31Z Content type: tutorial Language: en Sources: [TimDbg]() Topics: [debug](), [debugging](), [MSVC](), [Security](), [Variable]() Tags: [bug](), [crash](), [debug](), [debugger](), [debugging](), [local-variables](), [memory](), [msvc](), [security](), [stack]() ### AI overview This article explains why debuggers can produce misleading stack walks, focusing on stack corruption caused by buffer overflows that overwrite return addresses. It discusses how MSVC's /GS security checks affect crash stacks and recommends enabling /GS, along with using memory access breakpoints to investigate corruption. ### Source excerpt There are lots of reasons your debugger might be lying to you. Sometimes it's because information is lost when compiling due to optimizations. Sometimes the symbolic debug information isn't expressive enough. Other times it can be due to a bug in the debugger (although I hope that reason is rare). One frustrating case where the debugger sometimes "lies" to you is the stack walk. It's the single most important piece of information to come out of a crash, so when the stack walk is wrong, it's probably going to make analysis difficult. ## Newsletter 101 - July 2021 news DevFeed: [Newsletter 101 - July 2021 news]() Original publisher: [Read original article]() Published: 2021-08-01T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Kernel](), [gcc](), [MSVC](), [Linux](), [macOS](), [Windows]() Tags: [free](), [gcc](), [kernel](), [linux](), [macos](), [msvc](), [news](), [open-source](), [os](), [react](), [reactos](), [release](), [win32](), [winapi]() ### AI overview ReactOS Newsletter 101 reports project changes from February through July 2021. It highlights improved stability for amd64 builds, completed Structured Exception Handling support, a fix enabling semi-stable virtual-machine booting, planned GCC support in RosBE 2.3, restored i686 APIC support, and ongoing SMP work for multicore systems. ### Source excerpt Hello ReactOS followers! This report covers changes in the project during February-July 2021. And we definitely have some things to highlight! amd64 build is getting more stable Timo Kreuzer (tkreuzer) worked hard on various parts of the kernel and HAL, fixing issues here and there. Structured Exception Handling (SEH) support for the amd64 architecture was finished, various bugs around the kernel are fixed. A major issue with interrupt handling in HAL was also fixed in May, which finally allowed a semi-stable boot in a virtual environment. ## Релиз CLion 2021.2: улучшения в отладчике, проверка времени жизни объектов, поддержка CMake Presets DevFeed: [Релиз CLion 2021.2: улучшения в отладчике, проверка времени жизни объектов, поддержка CMake Presets]() Original publisher: [Read original article]() Author: anastasiak2512 (JetBrains) Published: 2021-07-29T13:29:29Z Content type: release Language: ru Sources: [JetBrains RU]() Topics: [CLion](), [C++](), [CMake](), [ide](), [Windows Subsystem for Linux](), [MSVC]() Tags: [autotools](), [c-plus-plus](), [cling](), [clion](), [cmake](), [debugger](), [freertos](), [ide](), [lifetimes](), [make](), [msvc](), [windows](), [wsl]() ### AI overview JetBrains presents CLion 2021.2, a cross-platform IDE for C and C++. The release adds protection against common C++ memory-access problems, CMake Build Presets support, GNU Autotools project support, remote-host and WSL profiling, debugger improvements, and Cling integration. ### Source excerpt Привет, Хабр! В конце июля в JetBrains стартует очередной релизный "паровоз". На этой неделе обновились многие IDE на платформе IntelliJ, на следующей запланированы обновления наших продуктов для .NET. И сегодня мы хотим поговорить о CLion 2021.2 -- новейшей версии нашей кроссплатформенной IDE для разработки на C и C++. Коротко о главном. CLion 2021.2 защитит ваш код от типичных проблем доступа к памяти в C++, автоматически загрузит настройки сборки приложения из CMake Build Presets, откроет проект с использованием GNU Autotools, поможет с профилированием на удаленном хосте и на WSL. Кроме того, значительно улучшен отладчик (самые крупные обновления ждут наших пользователей на Windows). А для тех, кто пока только изучает C++ или прототипирует новое приложение или библиотеку, мы добавили интеграцию с Cling -- интерпретатором С++. Дьявол в деталях ## Newsletter 100 - January 2021 news DevFeed: [Newsletter 100 - January 2021 news]() Original publisher: [Read original article]() Published: 2021-02-06T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Kernel](), [pull-requests](), [Cache](), [Windows](), [gcc](), [MSVC](), [USB]() Tags: [boot](), [bootloader](), [cache](), [filesystem](), [free](), [gcc](), [kernel](), [msvc](), [news](), [open-source](), [os](), [pull-requests](), [react](), [reactos](), [win32](), [winapi](), [windows]() ### AI overview ReactOS's January 2021 newsletter reports kernel development, including memory-manager and cache changes, improved Windows driver compatibility, GCC build progress, NTFS boot work, and USB boot improvements. ### Source excerpt Hello ReactOS followers! This is an attempt to re-instate the Newsletter, which informed you about recent developments. The previous Newsletter 99 was in 2013! This month we were mostly focused on the kernel work, merging pull requests and fixing regressions. Memory manager and Common cache work Being in development for almost six month, this work by Jérôme Gardou finally landed in the master branch. This change refactors many aspects of the Section Objects feature in NT-compatible kernel, making it more compatible with Windows. ## ReactOS in 2020 DevFeed: [ReactOS in 2020]() Original publisher: [Read original article]() Published: 2021-01-02T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Kernel](), [build tools](), [CMake](), [Filesystems](), [gcc](), [Shell](), [clang](), [Command-line interface](), [MSVC](), [GitHub]() Tags: [c-plus-plus](), [ci](), [clang](), [cmake](), [command-line](), [filesystem](), [free](), [gcc](), [github](), [kernel](), [msvc](), [open-source](), [os](), [react](), [reactos](), [shell](), [tooling](), [upgrade](), [win32](), [winapi]() ### AI overview A 2020 retrospective on ReactOS reports bug fixes, new instabilities, full-time kernel hires, shell improvements, RAPPS application-manager enhancements, and upgrades to its compiler and build tooling. It covers GCC 8.4, CMake 3.17, restored Clang CI builds, reduced older MSVC support, and a move to the C99 standard. ### Source excerpt Despite all the turbulence, it has been quite a productive year for ReactOS. Many bugs and instabilities were resolved, many more have been introduced. This year we hired two kernel developers full-time, this happened for the first time in the project's history. The post highlights some of the changes which may be interesting to the community. Shell changes Shell hasn't seen much attention recently, due to most of the work being concentrated in the kernel, but there are still some useful fixes and feature implementations: ## Syzkaller - Fuzzing ReactOS in 2020 DevFeed: [Syzkaller - Fuzzing ReactOS in 2020]() Original publisher: [Read original article]() Published: 2020-08-09T00:00:00Z Content type: tutorial Language: en Sources: [Front Page on ReactOS Website]() Topics: [Fuzzing/Fuzz testing](), [ReactOS](), [virtualization](), [winapi](), [MSVC](), [qemu](), [test-coverage](), [Oracle-VM-VirtualBox](), [Windows](), [GitHub Actions]() Tags: [code-coverage](), [free](), [fuzzing](), [github-actions](), [google-summer-of-code](), [msvc](), [open-source](), [os](), [qemu](), [react](), [reactos](), [virtualbox](), [virtualization](), [win32](), [winapi](), [windows]() ### AI overview This tutorial explains how to set up Syzkaller locally to fuzz ReactOS. It covers the required ReactOS build, virtualization software, Syzkaller and Golang setup, and reports that local fuzzing was running with about 110 WinAPI calls. It also describes ongoing work on Windows x86 support and KCOV-based code coverage. ### Source excerpt Hello everyone. In this blog post, I will be talking about the steps to set up Syzkaller for ReactOS locally and start fuzzing. If you have been following the blog posts on the ReactOS website then you would have noticed that this is my Google Summer of Code 2020 Project. Now that Coding period 2 has officially come to an end and the work is nearing completion, this post will help others in setting up the fuzzer get started with fuzzing. ## Binary rewriting with syzygy, Pt. I DevFeed: [Binary rewriting with syzygy, Pt. I]() Original publisher: [Read original article]() Author: Axel "0vercl0k" Souchet Published: 2017-08-05T23:08:00Z Content type: tutorial Language: en Sources: [Diary of a reverse-engineer]() Topics: [Instrumentation](), [toolchain](), [MSVC](), [x86](), [C++](), [function](), [Chromium]() Tags: [binaries](), [binary-rewriting](), [c-plus-plus](), [chromium](), [dynamic-binary-instrumentation](), [instrumentation](), [intel](), [misc](), [msvc](), [program-analysis](), [syzygy]() ### AI overview This introductory article presents Syzygy, Google's transformation tool chain for statically instrumenting PE images. It outlines the framework's capabilities and limitations and introduces analysis and transformation passes, including call-graph generation and rewriting functions in /GS-protected binaries. ### Source excerpt Introduction Binary instrumentation and analysis have been subjects that I have always found fascinating. At compile time via clang, or at runtime with dynamic binary instrumentation frameworks like Pin or DynamoRIO. One thing I have always looked for though, is a framework able to statically instrument a PE image. A ... ## GSoC xHCI status update DevFeed: [GSoC xHCI status update]() Original publisher: [Read original article]() Published: 2017-07-28T00:00:00Z Content type: opinion Language: en Sources: [Front Page on ReactOS Website]() Topics: [USB](), [Code](), [Data structures](), [implementation](), [function](), [MSVC](), [gcc]() Tags: [blog](), [code](), [compiler](), [data-structure](), [free](), [gsoc](), [implementation](), [msvc](), [open-source](), [os](), [react](), [reactos](), [update](), [usb](), [win32](), [winapi]() ### AI overview A GSoC progress update on ReactOS xHCI development. The author describes code cleanup, work on USB port status handling, an interrupt-related loop, ring memory allocation, alignment requirements, and the use of compiler-specific alignment directives in GCC and MSVC. ### Source excerpt In this post I'm going to detail my work progress. In the past week I've decided to clean up the code. Some parts of the code was re-written as functions. After that I've started working on the USB port status function. When an interrupt is generated the code is getting stuck in a loop. I'm trying to figure out what caused it. As we've discussed in the previous blog post. ## Here's a Standalone Cairo DLL for Windows DevFeed: [Here's a Standalone Cairo DLL for Windows]() Original publisher: [Read original article]() Author: Jeff Preshing Published: 2017-05-29T10:22:00Z Content type: article Language: en Sources: [Jeff Preshing]() Topics: [Library](), [C](), [Windows](), [MSVC](), [CMake](), [GitHub](), [Open Source](), [x86](), [Linux](), [macOS]() Tags: [c](), [cmake](), [github](), [graphics](), [graphs](), [libraries](), [linux](), [macos](), [msvc](), [open-source](), [windows](), [x86]() ### AI overview The article presents standalone Cairo DLLs for Windows, packaged with headers, import libraries, and x86/x64 binaries. The DLLs are statically linked, have no external dependencies, support MSVC applications, and use FreeType for text rendering. A GitHub build script and a CMake sample application are also provided. ### Source excerpt Cairo is an open source C library for drawing vector graphics. I used it to create many of the diagrams and graphs on this blog. Cairo is great, but it's always been difficult to find a precompiled Windows DLL that's up-to-date and that doesn't depend on a bunch of other DLLs. I was recently unable to find such a DLL, so I wrote a script to simplify the build process for one. The script is shared on GitHub: If you just want a binary package, you can download one from the Releases page: The binary package contains Cairo header files, import libraries and DLLs for both x86 and x64. The DLLs are statically linked with their own C runtime and have no external dependencies. Since Cairo's API is pure C, these DLLs should work with any application built with any version of MSVC. I configured these DLLs to render text using FreeType because I find the quality of FreeType-rendered text better than Win32-rendered text, which Cairo normally uses by default. FreeType also supports more font formats and gives text a consistent appearance across different operating systems. Sample Application Using CMake Here's a small Cairo application to test the DLLs. It uses CMake to support multiple platforms including Windows, MacOS and Linux. Hope this helps somebody! ## Cracking simple LCG PRNG DevFeed: [Cracking simple LCG PRNG]() Original publisher: [Read original article]() Published: 2017-03-01T23:00:00Z Content type: tutorial Language: en Sources: [Dennis Yurichev]() Topics: [Security](), [MSVC](), [Code](), [Unix]() Tags: [code](), [msvc](), [security](), [unix]() ### AI overview This article demonstrates how to recover the 32-bit state of an MSVC rand()-based linear congruential generator from observations of a color-lines game. It uses brute force to predict future ball placements and explains why LCGs are unsuitable for security-sensitive randomness. ### Source excerpt Cracking simple LCG PRNG ## Word 2010 support - Weekly report - Part 1: Installation DevFeed: [Word 2010 support - Weekly report - Part 1: Installation]() Original publisher: [Read original article]() Published: 2016-11-19T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Windows](), [MSVC](), [Oracle-VM-VirtualBox](), [debug](), [monitor](), [Testing]() Tags: [debugging](), [free](), [monitoring](), [msvc](), [open-source](), [os](), [react](), [reactos](), [report](), [testing](), [virtualbox](), [weekly](), [win32](), [winapi](), [windows]() ### AI overview This first weekly report describes preparing ReactOS and Windows Server 2003 virtual machines to test Word 2010 installation and compatibility. It covers MSVC builds, VirtualBox configuration, debugging and tracing tools, VM snapshots, and limitations of several monitoring tools on ReactOS. ### Source excerpt Hello everyone, I am Hermès Bélusca-Maïto. This is my first week report, as part of the part-time scholarship that I started two weeks ago, that consists in making ReactOS being able to support Word 2010. Preliminaries Before starting anything with Word 2010 I needed to prepare a testing environment. Because I am a native Windows user, I use a ReactOS trunk build made with the MSVC compiler. This ReactOS build was then properly installed and adequately configured on a VirtualBox (VBox) virtual machine (VM). ## NTFS Write Support GSoC - Week 2 DevFeed: [NTFS Write Support GSoC - Week 2]() Original publisher: [Read original article]() Published: 2016-06-06T00:00:00Z Content type: opinion Language: en Sources: [Front Page on ReactOS Website]() Topics: [Filesystems](), [ReactOS](), [Windows](), [MSVC](), [systems]() Tags: [free](), [msvc](), [open-source](), [os](), [react](), [reactos](), [systems](), [win32](), [winapi](), [windows]() ### AI overview A week-two progress report on ReactOS NTFS write support. The author resolved MSVC build problems, updated configure.cmd, and documented an existing limited capability to overwrite file contents without changing file size. Support for changing file sizes is still in progress, with file creation, renaming, and deletion planned as more difficult future work. ### Source excerpt This week I spent a few days hammering out all the problems I was having with MSVC builds, understanding exactly what was causing them, and updating configure.cmd so nobody else would have them in the future. See my forum post for the details. I've also been doing a lot of reading this week, both on the peculiarities of NTFS, and on Windows file system drivers. File System Forensic Analysis by Brain Carrier has been an incredible resource for the former, and Windows Nt File System Internals by Rajeev Nagar has been indispensable for the latter. [Next page]()