All compiler and build directories created on its own. Here is what is expected from VS Code in Windows: An automated scan for standard directories as soon as VS Code is fired / or C environment is setup for the first time. Unless I manually go and tweak each one of my programs. The version /2019 gets appended and in the end it renders my code useless. But of-course it is too much to expect.Įven now as Build Tools for Visual Studio 2019 RC is making its release. Proof of concepts etc, who don't need project management. Which is VS Code (which has an integrated debugger) will work with Visual Studio Build Tools on Windows environment.īasically this would have been an epic solution for standard 300-400 line C programs. I have given up on having an idea that a lightweight solution. OS : Latest Windows 10 and latest Visual Studio Code with up to date extension ms-vscode.cpptools 0.16.1.Īs an original poster of this thread. This is somewhat unrealistic that include folder is inside version 8, which would mean in case of change in version number would leave the code pretty much useless. "C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/MSBuild/15.0/Bin" "C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/", "C:/Program Files (x86)/Windows Kits/10/Include/0.0/ucrt"
"C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/VC/Tools/MSVC/8/include", "C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/*",
0 kommentar(er)
