


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.
