#1, at first, doesn’t seem to be a huge deal but if you plan to go with Remote-SSH development scenario (and for me it was a primary case) it becomes a real obstacle because you are no longer of direct control of how you launch Visual Studio Code. … to run Visual Studio Code from within Developer Command Prompt for Visual Studio.Visual Studio Code documentation for C/C++ development with Microsoft Visual C++ compiler have two requires: While everything described in this post was focused on local environment it is good to know that all of these instructions are also valid in Remote-SSH scenarios. In this post I would like to share how you can configure Visual Studio Code to build, test and debug Visual Studio C++ project. NET, I was expecting somewhat similar but it turned out to be not that simple, especially if you don’t want to cut off Visual Studio completely. So for me it was kind of logical and full of sense step to move my C/Win32 API development from Visual Studio to Visual Studio Code, and having previously a slick transition experience in. NET Core I’ve found myself doing almost all my coding in Visual Studio Code and to be honest I get used to its simplicity and blazing speed. However, in a last few years working with.

Why I am telling this? Because it won’t be a surprise, all my C/C++ projects were always written in Visual Studio with all it’s goodies like IntelliSense, projects support and extensions like Visual Assist. I am not a professional C/C++ developer nor Windows internals specialist, however I like to write in C.

I started to code in C/Win32 API in the university and I continue to do this almost every day. Starting from 0 (as the result of this PR) Visual Studio Code documentation has been updated to include information about how to run Visual Studio Code outside of Developers Command Prompt.However, if you are interested in a story of how this happened or you need to run and debug Visual Studio tests using right from Visual Studio Code then, I invite you to continue reading the post.

Visual studio code debug nunit tests