# Visual Studio Visual Studio is an integrated development environment and code editor for software development. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## CodeSOD: Extremely One Line DevFeed: [CodeSOD: Extremely One Line]() Original publisher: [Read original article]() Author: Remy Porter Published: 2026-09-16T06:30:00Z Content type: opinion Language: en Sources: [The Daily WTF]() Topics: [ASP.NET](), [Code](), [Visual Studio](), [Command-line interface](), [browser](), [HTTP]() Tags: [asp-net](), [browser](), [cli](), [code](), [codesod](), [http](), [studio]() ### AI overview This CodeSOD commentary examines an ancient ASP .Net application containing a function written on one line, Safari user-agent detection, and a mysterious "uplevel" value. It criticizes the confusing style and notes that the same pattern appears on multiple pages. ### Source excerpt Autoformatting your code is a standard thing to do these days. And in those days past, if we're being honest. There's no excuse to not use some kind of autoformatter. Whether you configure your editor to do it or are a weirdo like me who runs a formatter from the CLI as a build step, you've got an easy way to format your code so it looks neat and readable. And some IDEs, like Visual Studio, are pretty insistent about doing this for you. Which makes today's code sample a bit more perplexing. This comes from an ancient ASP .Net application that Austin has the misfortune to work with: protected void Page_PreInit(object sender, EventArgs e){if (Request.ServerVariables["http_user_agent"].IndexOf("Safari", StringComparison.CurrentCultureIgnoreCase) != -1)Page.ClientTarget = "uplevel";} protected void Page_Load(object sender, EventArgs e) { Logic(); } Which function is Logic() called from? The fact that I'm asking probably is enough to get you to scroll over. The entire Page_PreInit function is on a single line, followed by the declaration of the Page_Load function. A confusing and annoying choice. The real bonus is that if the browser has "Safari" in its user agent, we set a field to a mysterious "uplevel" value. A mix of user agent sniffing, strings as enums/flags, and wonderfully unclear names. And yes, this particular pattern appears in more than one page in Austin's application. Someone thought this was not just a good idea, but good enough to do over and over again. [Advertisement] Picking up NuGet is easy. Getting good at it takes time. Download our guide to learn the best practice of NuGet for the Enterprise. ## Improving Test Coverage in the Interview Coach Application with GitHub Copilot DevFeed: [Improving Test Coverage in the Interview Coach Application with GitHub Copilot]() Original publisher: [Read original article]() Author: Aaron Powell Published: 2026-09-15T16:00:21Z Content type: tutorial Language: en Sources: [Visual Studio Blog]() Topics: [test-coverage](), [Test coverage](), [GitHub Copilot](), [App](), [Visual Studio](), [Code]() Tags: [agent](), [analysis](), [code-coverage](), [copilot](), [github-copilot](), [productivity](), [projects](), [run](), [test](), [test-coverage](), [testing](), [tests](), [unit-tests](), [visual-studio]() ### AI overview This tutorial explains how to improve test coverage in the Interview Coach application by establishing a baseline, using GitHub Copilot's Test Agent to generate unit tests, and analyzing coverage across the solution. The article reports coverage increasing from 37% to 81%. ### Source excerpt Today I want to look at how we can improve on the test coverage that we have in the Interview Coach application. This application has some unit tests in it already, but I'm sure there is room for improvement. Defining our baseline Before we start writing tests, it's a good idea to have a baseline [...] The post Today I will... improve test coverage appeared first on Visual Studio Blog. ## 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. ## 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 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. ## Build Azure Skills Faster with Cloud Academy, a Visual Studio Subscriber Benefit DevFeed: [Build Azure Skills Faster with Cloud Academy, a Visual Studio Subscriber Benefit]() Original publisher: [Read original article]() Author: James Rempt Published: 2026-08-04T14:00:38Z Content type: article Language: en Sources: [Visual Studio Blog]() Topics: [Azure](), [Visual Studio](), [Cloud](), [Artificial Intelligence](), [DevOps](), [Automation](), [workflow automation](), [Prompt Engineering]() Tags: [ai](), [automation](), [azure](), [cloud](), [devops](), [learn](), [learning](), [prompt-engineering](), [visual-studio](), [visual-studio-subscriptions]() ### AI overview This article presents Cloud Academy as a Visual Studio subscriber benefit for building practical Azure skills. It highlights hands-on labs, certification-focused learning paths, assessments, sandbox experimentation, and AI-powered guidance, with examples spanning Azure administration, deployment, DevOps, security, cost optimization, Azure AI, and prompt engineering. ### Source excerpt If you've been looking for a practical way to build Azure skills, Cloud Academy (a QA company) gives Visual Studio subscribers hands-on learning that fits into busy schedules. Whether you're new to Azure, expanding your cloud expertise, working towards certifications or preparing for more advanced projects, this benefit helps you learn by doing. What you'll find in Cloud Academy The Cloud Academy benefit gives Visual Studio subscribers a flexible [...] The post Build Azure Skills Faster with Cloud Academy, a Visual Studio Subscriber Benefit appeared first on Visual Studio Blog. ## Creating custom PowerToys Run plugins DevFeed: [Creating custom PowerToys Run plugins]() Original publisher: [Read original article]() Author: {"twitter"=\>"hlaueriksson"} Published: 2024-02-13T22:00:00Z Content type: tutorial Language: en Sources: [Henrik Lau Eriksson]() Topics: [Microsoft PowerToys](), [Development](), [Visual Studio](), [GitHub](), [WPF](), [NuGet]() Tags: [blog](), [c-sharp](), [github](), [guide](), [how-to](), [net](), [nuget](), [nuget-package](), [plugins](), [powertoys](), [run](), [visual-studio]() ### AI overview A step-by-step guide to creating community plugins for PowerToys Run, covering project setup, Visual Studio, WPF dependencies, metadata, and NuGet packages. ### Source excerpt A step by step guide on how to create community plugins for PowerToys Run ## Symbol and Binary Indexing DevFeed: [Symbol and Binary Indexing]() Original publisher: [Read original article]() Author: Tim Misiak Published: 2022-08-10T15:30:09Z Content type: tutorial Language: en Sources: [TimDbg]() Topics: [debugging](), [Windows](), [Visual Studio]() Tags: [binaries](), [debug](), [debugger](), [debugging](), [files](), [symbols](), [windbg](), [windows]() ### AI overview This article explains why WinDbg debugging benefits from indexing both symbols and binaries. Symbols provide names, type definitions, and source files, while indexed binaries help debuggers reconstruct missing module data and perform reliable stack walking, especially when analyzing crash dumps from another machine. ### Source excerpt Symbol indexing is one of those features of WinDbg that can make things "just work" in a way that seems like magic. But it can also be the most painful things when it goes wrong. Why should I index symbols and binaries? Most of us have tried to debug without symbols at one point, and it can quickly become an exercise in frustration. It's much more productive to debug an executable where you have symbols because it gives you function names, variable names, type definitions, and source files. ## Software failures, invisible complexity, and the limits of code DevFeed: [Software failures, invisible complexity, and the limits of code]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2022-06-18T07:00:00Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [Code](), [Software](), [Hardware](), [Visual Studio](), [Fortran]() Tags: [code](), [hardware](), [nasa](), [software](), [visual-studio]() ### AI overview This commentary examines how software can fail despite executing its instructions correctly, arguing that failures often arise from misunderstood requirements and the invisible complexity of computing. It discusses software-related safety investigations, Visual Studio's scale, and how programming languages and interfaces shape how people understand code. ### Source excerpt A good friend of mine who's worked on some pretty pivotal hardware/software integrations for our time told me: "it feels like a miracle when I see the code I wrote drive physical bits. I almost can't believe it. No seriously... how does this even work?". If this sentiment resonates with you to some level, you will love reading this article: The coming software apocalypse ## This entire article is fascinating. It took a lot of restraint not to just pull-quote every paragraph from this article. The software did exactly what it was told to do. In fact it did it perfectly. The reason it failed is that it was told to do the wrong thing. Software failures are failures of understanding, and of imagination. This is the trouble with making things out of code, as opposed to something physical. "The complexity," as Leveson puts it, "is invisible to the eye." ..."Computing is fundamentally invisible," Gerard Berry said in his talk. "When your tires are flat, you look at your tires, they are flat. When your software is broken, you look at your software, you see nothing." The National Highway Traffic Safety Administration enlisted software experts from NASA to perform an intensive review of Toyota's code. After nearly 10 months, the NASA team hadn't found evidence that software was the cause -- but said they couldn't prove it wasn't. ... They showed that as little as a single bit flip -- a one in the computer's memory becoming a zero or vice versa -- could make a car run out of control." "Visual Studio is one of the single largest pieces of software in the world," he said. "It's over 55 million lines of code. And one of the things that I found out in this study is more than 98 percent of it is completely irrelevant. All this work had been put into this thing, but it missed the fundamental problems that people faced. And the biggest one that I took away from it was that basically people are playing computer inside their head. ... So the students who did well -- in fact the only ones who survi ## Detect kernel information disclosure by Bochspwn-reloaded - GSoC 2020 - First week DevFeed: [Detect kernel information disclosure by Bochspwn-reloaded - GSoC 2020 - First week]() Original publisher: [Read original article]() Published: 2020-06-04T00:00:00Z Content type: tutorial Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Instrumentation](), [Visual Studio](), [Assembly](), [Bash](), [Vcpkg]() Tags: [bash](), [free](), [gsoc](), [instrumentation](), [open-source](), [os](), [react](), [reactos](), [studio](), [vcpkg](), [win32](), [winapi]() ### AI overview A ReactOS GSoC student reports the first week of a project using bochspwn-reloaded to detect kernel information disclosure and uninitialized memory use. The article describes changes to stack-trace formatting, source lookup for inline and non-inline functions, and compiling the tool with Visual Studio 2019. ### Source excerpt Introduction Hello, I am Nguyen Trung Khanh (@khanhnt) from Vietnam and I am one of the GSoC students of ReactOS. My project is running ReactOS on bochspwn-reloaded to list and fix all the bugs which were found by the tool. Additionally, I have a week to implement detection of uninitialized memory use. The first week Before GSoC, I did compile bochspwn-reloaded and run ReactOS on it so my work in the first week is pretty easy. ## ReactOS Build Environment 2.2 released DevFeed: [ReactOS Build Environment 2.2 released]() Original publisher: [Read original article]() Published: 2020-05-01T00:00:00Z Content type: release Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [build tools](), [gcc](), [toolchain](), [Parser](), [C](), [C++](), [CMake](), [Visual Studio](), [Linux](), [macOS](), [Windows]() Tags: [binutils](), [build](), [c](), [c-plus-plus](), [cmake](), [compiler](), [free](), [gcc](), [linux](), [macos](), [open-source](), [os](), [react](), [reactos](), [toolchain](), [visual-studio](), [win32](), [winapi]() ### AI overview ReactOS Build Environment 2.2 upgrades the project's compiler and build tools, replacing GCC 4.7.2 with GCC 8.4.0. The release improves diagnostics, adds support for newer C and C++ standards, includes Bison and Flex, and updates the remaining toolchain. ### Source excerpt The ReactOS Build Environment (RosBE), our curated set of compilers and build tools, has just received a major upgrade. After more than 7 years of using the same and now ancient GCC 4.7.2, ReactOS is finally going to be built with the help of a modern compiler (GCC 8.4.0). Among other things, the new version better detects programming mistakes like improperly sized buffers, and comes with improved error messages to pinpoint such mistakes to the corresponding position in code. ## Espressif's September 2018 updates: ESP-IDF v3.0.3, ESP Mesh, and IoT ecosystem news DevFeed: [Espressif's September 2018 updates: ESP-IDF v3.0.3, ESP Mesh, and IoT ecosystem news]() Original publisher: [Read original article]() Author: John Lee Published: 2018-09-06T00:00:00Z Content type: news Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Internet of things](), [ESP32](), [Wi-Fi](), [Azure](), [Bluetooth](), [Arduino](), [Visual Studio](), [Python]() Tags: [arduino](), [azure](), [blog](), [esp-idf](), [esp-idf-v3-0](), [esp32](), [esp8266](), [espressif](), [here](), [internet-of-things](), [iot](), [lwip](), [newsletter](), [python](), [visual-studio](), [wi-fi]() ### AI overview Espressif's September 2018 roundup covers the ESP-IDF v3.0.3 bugfix release, ESP Mesh for expanded Wi-Fi coverage, Azure IoT Workbench support for Arduino development on ESP32, and community events and ESP32-based devices. ### Source excerpt Hi everyone, It seems that the scorching heat of summer in Shanghai has only fueled our fervor for improving our IoT solutions! We have been hard at work releasing ESP-IDF v3.0.3. This bugfix update is compatible with all apps written for ESP-IDF v.3.0.x. The changes are related to Bluetooth, LWIP, Wi-Fi, System, and Driver. You can check the entire list of changes here, while you can have a look at the ESP-IDF Programming Guide for all the installation instructions. ## How to Build a CMake-Based Project DevFeed: [How to Build a CMake-Based Project]() Original publisher: [Read original article]() Author: Jeff Preshing Published: 2017-05-11T12:30:00Z Content type: tutorial Language: en Sources: [Jeff Preshing]() Topics: [CMake](), [C++](), [Linux](), [macOS](), [Windows](), [Caching](), [Command-line interface](), [make](), [Visual Studio](), [Xcode](), [OpenGL]() Tags: [build](), [c-plus-plus](), [cache](), [cmake](), [command-line](), [gui](), [how-to](), [linux](), [macos](), [visual-studio](), [windows](), [xcode]() ### AI overview A practical guide to configuring and building CMake-based C/C++ projects across Windows, macOS, and Linux. It explains source and binary folders, generated build pipelines, CMake's cache, and several command-line and graphical workflows. ### Source excerpt CMake is a versatile tool that helps you build C/C++ projects on just about any platform you can think of. It's used by many popular open source projects including LLVM, Qt, KDE and Blender. All CMake-based projects contain a script named CMakeLists.txt, and this post is meant as a guide for configuring and building such projects. This post won't show you how to write a CMake script - that's getting ahead of things, in my opinion. As an example, I've prepared a CMake-based project that uses SDL2 and OpenGL to render a spinning 3D logo. You can build it on Windows, MacOS or Linux. The information here applies to any CMake-based project, so feel free to skip ahead to any section. However, I recommend reading the first two sections first. The Source and Binary Folders The Configure and Generate Steps Running CMake from the Command Line Running cmake-gui Running ccmake Building with Unix Makefiles Building with Visual Studio Building with Xcode Building with Qt Creator Other CMake Features If you don't have CMake yet, there are installers and binary distributions on the CMake website. In Unix-like environments, including Linux, it's usually available through the system package manager. You can also install it through MacPorts, Homebrew, Cygwin or MSYS2. The Source and Binary Folders CMake generates build pipelines. A build pipeline might be a Visual Studio .sln file, an Xcode .xcodeproj or a Unix-style Makefile. It can also take several other forms. To generate a build pipeline, CMake needs to know the source and binary folders. The source folder is the one containing CMakeLists.txt. The binary folder is where CMake generates the build pipeline. You can create the binary folder anywhere you want. A common practice is to create a subdirectory build beneath CMakeLists.txt. By keeping the binary folder separate from the source, you can delete the binary folder at any time to get back to a clean slate. You can even create several binary folders, side-by-side, that use diffe ## USB stack improvements GSoC - Week 11 DevFeed: [USB stack improvements GSoC - Week 11]() Original publisher: [Read original article]() Published: 2016-08-10T00:00:00Z Content type: opinion Language: en Sources: [Front Page on ReactOS Website]() Topics: [USB](), [Development](), [ide](), [debug](), [Git](), [Visual Studio](), [patches](), [Linux](), [jira]() Tags: [debugger](), [development](), [free](), [git](), [ide](), [jira](), [linux](), [open-source](), [os](), [patches](), [react](), [reactos](), [usb](), [visual-studio](), [win32](), [winapi]() ### AI overview A GSoC Week 11 progress report on ReactOS USB stack work. The author moved development and testing from 2k3 to ReactOS, configured Visual Studio 2015 and WinDbg, resolved build issues, and worked on synchronizing Git and SVN repositories while testing Jira issues. ### Source excerpt I spent last week moving from 2k3 to ROS. After doing final validation of my usbhub changes on 2k3, me and my mentor decided to move to some real world issues. I have setup my development and testing environment work with ROS instead of 2k3. VS-2015 as IDE for ROS First of all, I decided to use VS as IDE, to be able to use windbg as debugger. In that case I'll have minimal changes on workflow I was using on 2k3 before. ## Solidity Available in Visual Studio DevFeed: [Solidity Available in Visual Studio]() Original publisher: [Read original article]() Author: Vitalik Buterin Published: 2016-03-30T20:17:25Z Content type: news Language: en Sources: [Ethereum Foundation Blog]() Topics: [Solidity](), [Visual Studio](), [ide](), [Ethereum](), [Blockchain](), [Microsoft](), [Programming language](), [Development](), [Programming]() Tags: [blockchain](), [blockchain-technology](), [compilation](), [deployment](), [developers](), [development](), [ethereum](), [extension](), [integration](), [microsoft](), [programming-language](), [research-development](), [smart-contract](), [ui](), [visual-studio]() ### AI overview ConsenSys and Microsoft announced that Solidity would be available in Microsoft Visual Studio. The integration provides project scaffolding, smart contract samples, ABI and binary generation, compilation and deployment menus, and an automatically generated interface for testing contract calls across Ethereum deployments. ### Source excerpt Consensys and Microsoft have announced that the Ethereum contract programming language Solidity will be available in Microsoft's Visual Studio integrated development environment. ConsenSys and Microsoft collaborated on this integration to enable developers to rapidly build smart contract-based applications for the public Ethereum blockchain, as well as private and consortium blockchain... ## Publishing a ASP.NET 5 Web-Application to IIS Locally DevFeed: [Publishing a ASP.NET 5 Web-Application to IIS Locally]() Original publisher: [Read original article]() Author: Abhinaba Basu \[MSFT\] Published: 2015-12-22T18:10:48Z Content type: tutorial Language: en Sources: [Abhinaba Basu]() Topics: [ASP.NET](), [web applications](), [Visual Studio](), [Windows](), [Firewall](), [Web Development]() Tags: [asp-net](), [firewall](), [visual-studio](), [web](), [windows]() ### AI overview A practical guide to publishing an ASP.NET 5 web application to IIS locally using Visual Studio and file system publishing, then configuring IIS to serve the application. It also explains enabling Windows Firewall access and finding the local IP address so other devices on the same network can connect. ### Source excerpt I ran into few issues and discovered some kinks in publishing the new ASP.NET 5 Web-Application to... ## Migrate from TFS to Git DevFeed: [Migrate from TFS to Git]() Original publisher: [Read original article]() Published: 2015-03-24T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Git](), [GitLab](), [Command-line interface](), [Visual Studio](), [cross-platform]() Tags: [command-line](), [cross-platform](), [git](), [gitlab](), [microsoft](), [tools](), [visual-studio]() ### AI overview This tutorial explains how to migrate projects from Microsoft Team Foundation Server (TFS) to Git while preserving repository history. It discusses Git-TF and git-tfs, including their use for exporting TFS repositories and working with TFS-related services. ### Source excerpt Lorem ipsum dolor sit amet ## ReactOS Development Report: Setting Up and Compiling in a Windows Server 2003 Virtual Machine DevFeed: [ReactOS Development Report: Setting Up and Compiling in a Windows Server 2003 Virtual Machine]() Original publisher: [Read original article]() Published: 2014-06-14T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Development](), [Windows](), [Visual Studio](), [Code](), [cpu]() Tags: [code](), [cpu](), [development](), [free](), [open-source](), [os](), [react](), [reactos](), [visual-studio](), [win32](), [winapi](), [windows]() ### AI overview A ReactOS development report describes setting up a development environment in a Windows Server 2003 virtual machine, installing Visual Studio 2010 and RosBE, and compiling the source code. The excerpt reports that compilation was very slow with one CPU core and notes bugs in Visual Studio 2010. ### Source excerpt As I said in the last report, the week began by setting up a development environment in a Windows Server 2003 VM. I had to install Visual Studio 2010 and RosBE, and then download and compile the source code to verify that everything was working correctly. When I tried to compile, I realized two things. First, that vs2010 is much buggier than I remembered, and second, that compiling in a Virtual Machine with one cpu core is very very slow. ## Automating the build of MSI setup packages on Jenkins DevFeed: [Automating the build of MSI setup packages on Jenkins]() Original publisher: [Read original article]() Published: 2014-03-11T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Jenkins](), [Visual Studio]() Tags: [build](), [compilation](), [how-to](), [jenkins]() ### AI overview A how-to guide for automating MSI setup package builds on Jenkins. It explains why Visual Studio setup projects require Visual Studio rather than the usual MSBuild plugin, and recommends using devenv.com instead of devenv.exe so the build runs synchronously in the Jenkins console. ### Source excerpt Lorem ipsum dolor sit amet ## Shell experiments: Progress on the start menu DevFeed: [Shell experiments: Progress on the start menu]() Original publisher: [Read original article]() Published: 2014-02-16T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Shell](), [Windows](), [Visual Studio](), [Code](), [implementation](), [debug]() Tags: [code](), [debugging](), [free](), [implementation](), [logs](), [open-source](), [os](), [react](), [reactos](), [shell](), [toolbar](), [visual-studio](), [win32](), [winapi](), [windows]() ### AI overview A ReactOS development update describes progress on implementing CMenuSite and CMenuBand for the Start Menu. The work uses rshell to test alternative shell32 implementations in Visual Studio, logs calls to Windows' CMenuBand, and applies findings to improve menu display and sizing. ### Source excerpt Work, this week, began with finishing the initial implementation of CMenuSite. This class and the window it creates act as an intermediary between a BaseBar and a MenuBand, forwarding the events and messages either to the child band, or to the parent bar, as necessary. It handles the sizing of the child band, to adapt it to changes in the available space. It also provides certain services related to the positioning and sizing of the child bar, which it handles by forwarding some requests to the child, and the rest to the parent. ## 'object' does not contain a definition for 'errors' DevFeed: ['object' does not contain a definition for 'errors']() Original publisher: [Read original article]() Published: 2013-08-29T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Exception](), [Testing](), [ASP.NET](), [Visual Studio]() Tags: [api](), [asp-net](), [errors](), [exception](), [exceptions](), [testing](), [unit-test](), [visual-studio]() ### AI overview A unit test for an ASP.NET Web API exception filter fails when it tries to inspect the anonymous object returned for validation errors. The article explains that the anonymous type is not visible outside the tested Api assembly and shows that adding InternalsVisibleTo to Api.csproj makes the test pass. ### Source excerpt Lorem ipsum dolor sit amet ## ReactOS Newsletter 97: C++ Visual Studio Build Support and USB Fixes DevFeed: [ReactOS Newsletter 97: C++ Visual Studio Build Support and USB Fixes]() Original publisher: [Read original article]() Published: 2013-07-01T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [C++](), [stl](), [Visual Studio](), [Testing](), [USB](), [Oracle-VM-VirtualBox]() Tags: [c-plus-plus](), [free](), [open-source](), [os](), [react](), [reactos](), [stl](), [testing](), [usb](), [virtualbox](), [visual-studio](), [win32](), [winapi]() ### AI overview This ReactOS newsletter discusses support for building ReactOS's C++ components with Visual Studio, including an STLport-based solution, and describes USB fixes found through testing with VirtualBox USB passthrough. ### Source excerpt C++ One of the last big missing pieces of building ReactOS using Visual Studio was support for C++. In ReactOS, the biggest piece of C++ code is explorer, without which users have no graphical shell when ReactOS boots up. Support for C++ requires not just a compiler capable of building C++ code, but also the presence of the standard template library. For developers where C++ was their first language, usage of the STL is fairly common and it is almost guaranteed to be linked in by default regardless of whether it is used or not. ## Setting up a WPF Application With PRISM DevFeed: [Setting up a WPF Application With PRISM]() Original publisher: [Read original article]() Published: 2013-06-25T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [WPF](), [NuGet](), [Visual Studio](), [modules](), [ui]() Tags: [design-patterns](), [desktop](), [how-to](), [modules](), [nuget](), [plugins](), [visual-studio]() ### AI overview A tutorial on setting up a Windows Presentation Foundation (WPF) application with PRISM. It covers creating a WPF project, installing PRISM dependencies through NuGet, creating an application bootstrapper, and configuring a shell and modules using MEF for a modular plugin-based architecture. ### Source excerpt Lorem ipsum dolor sit amet ## Getting Started with Git and Visual Studio DevFeed: [Getting Started with Git and Visual Studio]() Original publisher: [Read original article]() Published: 2013-06-02T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Git](), [Visual Studio](), [Extension](), [resharper]() Tags: [bash](), [code](), [extension](), [extensions](), [git](), [install](), [installation](), [visual-studio]() ### AI overview A tutorial on setting up Git for use with Visual Studio. It discusses Visual Studio's Git extension, recommends Git Extensions for Windows and Git Source Control Provider, and explains how to install and configure them. ### Source excerpt Lorem ipsum dolor sit amet [Next page]()