Configure Visual Studio Code For Microsoft C++

Version 1.63 (/updates) is now available! Read about the new features and fixes from November.
×
IN THIS ARTICLE
Prerequisites
✏ Edit (https://github.com/microsoft/vscode-docs/blob/main/docs/cpp/config-msvc.md)
Overview (/docs) Create Hello World
{ Explore IntelliSense
SETUP
Configure VS Code for Microsoft C++ Build helloworld.cpp
GET STARTED Debug helloworld.cpp

In this tutorial, you configure Visual Studio Code to use the Microsoft Visual C++ compiler and debugger
USER GUIDE Step through the code
on Windows.
Set a watch
LANGUAGES
After configuring VS Code, you will compile and debug a simple Hello World program in VS Code. This C/C++ configurations
NODE.JS /
tutorial does not teach you details about the Microsoft C++ toolset or the C++ language. For those Reusing your C++
JAVASCRIPT
subjects, there are many good resources available on the Web. configuration
TYPESCRIPT Run VS Code outside the
If you have any problems, feel free to file an issue for this tutorial in the VS Code documentation Developer Command
PYTHON
repository (https://github.com/microsoft/vscode-docs/issues). Prompt
JAVA Troubleshooting
C++ Next steps
Intro Videos (/docs Prerequisites # (https://twitter.com/intent/tweet?original_referer=https:

/cpp/introvideos-cpp) Tweet//code.visualstudio.com/docs/cpp/config-msvc&ref_src=twsrc%5Etfw&
To successfully complete this tutorial, you must do the following: this text=Configure%20Visual%20Studio%20Code%20for%20Microsoft%20C++&
GCC on Linux (/docs
link tw_p=tweetbutton&url=https://code.visualstudio.com/docs/cpp/config-
/cpp/config-linux)
1. Install Visual Studio Code (/download). msvc&via=code)
GCC on Windows
Subscribe(/feed.xml)
(/docs/cpp/config- 2. Install the C/C++ extension for VS Code (https://marketplace.visualstudio.com
mingw) (https://stackoverflow.com
/items?itemName=ms-vscode.cpptools). You can install the C/C++ extension by searching for 'c++' Ask
/questions/tagged
GCC on Windows questions
in the Extensions view ( Ctrl+Shift+X ). /vscode)
Subsystem for Linux
(/docs/cpp/config-wsl) Follow (https://go.microsoft.com
@code/fwlink/?LinkID=533687)
Clang on macOS
Request(https://go.microsoft.com
(/docs/cpp/config-
features/fwlink/?LinkID=533482)
clang-mac)
(https://www.github.com
Microsoft C++ on Report
/Microsoft/vscode
Windows (/docs issues
/issues)
/cpp/config-msvc)
(https://www.youtube.com
Build with CMake Watch
/channel
(/docs/cpp/build-with- videos
/UCs5Y5_7XK8HLDX0SLNwkd3w)
cmake) 3. Install the Microsoft Visual C++ (MSVC) compiler toolset.
CMake Tools on Linux
(/docs/cpp/cmake- If you have a recent version of Visual Studio, open the Visual Studio Installer from the Windows Start
linux) menu and verify that the C++ workload is checked. If it's not installed, then check the box and select
Debugging (/docs the Modify button in the installer.
/cpp/cpp-debug)
Editing (/docs
You can also install the Desktop development with C++ workload without a full Visual Studio IDE
/cpp/cpp-ide) installation. From the Visual Studio Downloads (https://visualstudio.microsoft.com
/downloads#other) page, scroll down until you see Tools for Visual Studio 2019 under the All
Downloads section and select the download for Build Tools for Visual Studio 2019.
This will launch the Visual Studio Installer, which will bring up a dialog showing the available Visual
Studio Build Tools workloads. Check the Desktop development with C++ workload and select
Install.
Hello from Seattle. Follow @code (https://go.microsoft.com/fwlink/?LinkID=533687) Support (https://support.serviceshub.microsoft.com/supportforbusiness
/create?sapId=d66407ed-3967-b000-4cfb-2c318cad363d)
Star 125,931
Privacy (https://privacy.microsoft.com/privacystatement)
Terms of Use (https://www.microsoft.com/legal/terms-of-use) License (/License)
(https://www.microsoft.com)
© 2022 Microsoft
IN THIS ARTICLE
Prerequisites
Create Hello World
Explore IntelliSense
Build helloworld.cpp
Debug helloworld.cpp
Step through the code
Set a watch
C/C++ configurations
Reusing your C++

configuration
Note: You can use the C++ toolset from Visual Studio Build Tools along with Visual Studio Code to
compile, build, and verify any C++ codebase as long as you also have a valid Visual Studio license
Run VS Code outside the
Developer Command (either Community, Pro, or Enterprise) that you are actively using to develop that C++ codebase.
Prompt
Troubleshooting
Next steps
Check your Microsoft Visual C++ installation #
(https://twitter.com/intent/tweet?original_referer=https: To use MSVC from a command line or VS Code, you must run from a Developer Command Prompt for
Tweet//code.visualstudio.com/docs/cpp/config-msvc&ref_src=twsrc%5Etfw&
Visual Studio. An ordinary shell such as PowerShell, Bash, or the Windows command prompt does not
this text=Configure%20Visual%20Studio%20Code%20for%20Microsoft%20C++&
have the necessary path environment variables set.
msvc&via=code)
Subscribe(/feed.xml) To open the Developer Command Prompt for VS, start typing 'developer' in the Windows Start menu, and
(https://stackoverflow.com you should see it appear in the list of suggestions. The exact name depends on which version of Visual
Ask
questions
/questions/tagged Studio or the Visual Studio Build Tools you have installed. Select the item to open the prompt.
/vscode)
Follow (https://go.microsoft.com
Report
/Microsoft/vscode
issues
/issues)
Watch
/channel
videos
You can test that you have the C++ compiler, cl.exe , installed correctly by typing 'cl' and you should
see a copyright message with the version and basic usage description.
If the Developer Command Prompt is using the BuildTools location as the starting directory (you wouldn't
want to put projects there), navigate to your user folder ( C:\users\{your username}\ ) before you start
IN THIS ARTICLE creating new projects.
Prerequisites
Note: If for some reason you can't run VS Code from a Developer Command Prompt, you can find
Create Hello World
a workaround for building C++ projects with VS Code in Run VS Code outside a Developer
Command Prompt.
Set a watch Create Hello World #

C/C++ configurations From the Developer Command Prompt, create an empty folder called "projects" where you can store all
Reusing your C++ your VS Code projects, then create a subfolder called "helloworld", navigate into it, and open VS Code
configuration
( code ) in that folder ( . ) by entering the following commands:
Developer Command mkdir projects
Prompt cd projects
Troubleshooting mkdir helloworld
cd helloworld
Next steps
code .
(https://twitter.com/intent/tweet?original_referer=https:
The "code ." command opens VS Code in the current working folder, which becomes your "workspace".
Tweet//code.visualstudio.com/docs/cpp/config-msvc&ref_src=twsrc%5Etfw& As
you go through the tutorial, you will see three files created in a .vscode folder in the workspace:
msvc&via=code)
• tasks.json (build instructions)
• launch.json (debugger settings)
(https://stackoverflow.com
Ask
/questions/tagged • c_cpp_properties.json (compiler path and IntelliSense settings)
questions
/vscode)
@code/fwlink/?LinkID=533687) Add a source code file #
features/fwlink/?LinkID=533482) In the File Explorer title bar, select the New File button and name the file helloworld.cpp .
Report
/Microsoft/vscode
issues
/issues)
Watch
/channel
videos
Add hello world source code #

Now paste in this source code:
#include <iostream>
#include <vector>
#include <string>
IN THIS ARTICLE
using namespace std;
Prerequisites
int main()
Create Hello World
{
Explore IntelliSense vector<string> msg {"Hello", "C++", "World", "from", "VS Code", "and the C++ extensio
n!"};
Debug helloworld.cpp for (const string& word : msg)

{
cout << word << " ";
Set a watch }
C/C++ configurations cout << endl;
}
Reusing your C++
configuration
Now press Ctrl+S to save the file. Notice how the file you just added appears in the File Explorer view
Developer Command ( Ctrl+Shift+E ) in the side bar of VS Code:
Prompt
Troubleshooting
Next steps
msvc&via=code)
Ask
/questions/tagged
questions
/vscode)
You can also enable Auto Save (/docs/editor/codebasics#_saveauto-save) to automatically save your file
changes, by checking Auto Save in the main File menu.
The Activity Bar on the far left lets you open different views such as Search, Source Control, and Run.
features/fwlink/?LinkID=533482) You'll look at the Run view later in this tutorial. You can find out more about the other views in the VS
(https://www.github.com Code User Interface documentation (/docs/getstarted/userinterface).
Report
/Microsoft/vscode
issues
/issues)
Note: When you save or open a C++ file, you may see a notification from the C/C++ extension
Watch about the availability of an Insiders version, which lets you test new features and fixes. You can
/channel
videos
/UCs5Y5_7XK8HLDX0SLNwkd3w) ignore this notification by selecting the X (Clear Notification).
Explore IntelliSense #
In your new helloworld.cpp file, hover over vector or string to see type information. After the
declaration of the msg variable, start typing msg. as you would when calling a member function. You
should immediately see a completion list that shows all the member functions, and a window that shows
the type information for the msg object:
IN THIS ARTICLE
Prerequisites
Create Hello World
Step through the code You can press the Tab key to insert the selected member; then, when you add the opening parenthesis,
Set a watch you will see information about any arguments that the function requires.
Reusing your C++

configuration

Build helloworld.cpp #
Developer Command Next, you will create a tasks.json file to tell VS Code how to build (compile) the program. This task will
Prompt
invoke the Microsoft C++ compiler to create an executable file based on the source code.
Troubleshooting
Next steps From the main menu, choose Terminal > Configure Default Build Task. In the dropdown, which will
display a tasks dropdown listing various predefined build tasks for C++ compilers. Choose cl.exe build
active file, which will build the file that is currently displayed (active) in the editor.
msvc&via=code)
Ask
/questions/tagged
questions This will create a tasks.json file in a .vscode folder and open it in the editor.
/vscode)
Follow (https://go.microsoft.com Your new tasks.json file should look similar to the JSON below:
Request(https://go.microsoft.com {
features/fwlink/?LinkID=533482) "version": "2.0.0",
(https://www.github.com "tasks": [
Report
/Microsoft/vscode {
issues
/issues) "type": "shell",
"label": "cl.exe build active file",
Watch "command": "cl.exe",
/channel
videos "args": [
"/Zi",
"/EHsc",
"/Fe:",
"${fileDirname}\\${fileBasenameNoExtension}.exe",
"${file}"
],
"problemMatcher": ["$msCompile"],
"group": {
"kind": "build",
"isDefault": true
}
}
]
}
The command setting specifies the program to run; in this case that is "cl.exe". The args array specifies
the command-line arguments that will be passed to cl.exe. These arguments must be specified in the
order expected by the compiler. This task tells the C++ compiler to take the active file ( ${file} ),
compile it, and create an executable file ( /Fe: switch) in the current directory ( ${fileDirname} ) with
the same name as the active file but with the .exe extension ( ${fileBasenameNoExtension}.exe ),
resulting in helloworld.exe for our example.
Note: You can learn more about tasks.json variables in the variables reference (/docs/editor
/variables-reference).
IN THIS ARTICLE
The label value is what you will see in the tasks list; you can name this whatever you like.
Prerequisites
Create Hello World The problemMatcher value selects the output parser to use for finding errors and warnings in the
Explore IntelliSense compiler output. For cl.exe, you'll get the best results if you use the $msCompile problem matcher.
Build helloworld.cpp The "isDefault": true value in the group object specifies that this task will be run when you press
Debug helloworld.cpp Ctrl+Shift+B . This property is for convenience only; if you set it to false, you can still run it from the
Step through the code Terminal menu with Tasks: Run Build Task.
Set a watch
Reusing your C++

Running the build #
configuration
1. Go back to helloworld.cpp . Your task builds the active file and you want to build
helloworld.cpp .
Developer Command
Prompt
2. To run the build task defined in tasks.json , press Ctrl+Shift+B or from the Terminal main
Troubleshooting
menu choose Tasks: Run Build Task.
Next steps
3. When the task starts, you should see the Integrated Terminal panel appear below the source code
(https://twitter.com/intent/tweet?original_referer=https: editor. After the task completes, the terminal shows output from the compiler that indicates whether
this text=Configure%20Visual%20Studio%20Code%20for%20Microsoft%20C++& the build succeeded or failed. For a successful C++ build, the output looks something like this:
msvc&via=code)
Ask
/questions/tagged
questions
/vscode)
Report
/Microsoft/vscode
issues
/issues)
Watch
/channel
videos
If the build fails due to not finding cl.exe , or lacking an include path, make sure you have started VS
Code from the Developer Command Prompt for Visual Studio.
1. Create a new terminal using the + button and you'll have a new terminal (running PowerShell) with
the helloworld folder as the working directory. Run ls and you should now see the executable
helloworld.exe along with various intermediate C++ output and debugging files
( helloworld.obj , helloworld.pdb ).
2. You can run helloworld in the terminal by typing .\helloworld.exe .
IN THIS ARTICLE
Prerequisites
Note: You might need to press Enter a couple of times initially to see the PowerShell prompt in
Create Hello World

the terminal. This issue should be fixed in a future release of Windows.
Modifying tasks.json #
Step through the code You can modify your tasks.json to build multiple C++ files by using an argument like
Set a watch "${workspaceFolder}\\*.cpp" instead of ${file} . This will build all .cpp files in your current folder.
C/C++ configurations You can also modify the output filename by replacing
Reusing your C++
"${fileDirname}\\${fileBasenameNoExtension}.exe" with a hard-coded filename (for example
configuration "${workspaceFolder}\\myProgram.exe" ).
Developer Command
Prompt
Troubleshooting Debug helloworld.cpp #

Next steps
Next, you'll create a launch.json file to configure VS Code to launch the Microsoft C++ debugger when
(https://twitter.com/intent/tweet?original_referer=https: you press F5 to debug the program. From the main menu, choose Run > Add Configuration... and then
choose C++ (Windows).
You'll then see a dropdown for various predefined debugging configurations. Choose cl.exe build and
msvc&via=code)
debug active file.
Ask
/questions/tagged
questions
/vscode)
VS Code creates a launch.json file, opens it in the editor, and builds and runs 'helloworld'.
Report
/Microsoft/vscode
issues {
/issues)
"version": "0.2.0",
(https://www.youtube.com "configurations": [
Watch
/channel {
videos
/UCs5Y5_7XK8HLDX0SLNwkd3w) "name": "cl.exe build and debug active file",
"type": "cppvsdbg",
"request": "launch",
"program": "${fileDirname}\\${fileBasenameNoExtension}.exe",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [],
"externalConsole": false,
"preLaunchTask": "cl.exe build active file"
}
]
}
The program setting specifies the program you want to debug. Here it is set to the active file folder
${fileDirname} and active filename with the .exe extension ${fileBasenameNoExtension}.exe ,
which if helloworld.cpp is the active file will be helloworld.exe .
By default, the C++ extension won't add any breakpoints to your source code and the stopAtEntry
value is set to false . Change the stopAtEntry value to true to cause the debugger to stop on the
main method when you start debugging.
Start a debugging session #
IN THIS ARTICLE 1. Go back to helloworld.cpp so that it is the active file.
Prerequisites
2. Press F5 or from the main menu choose Run > Start Debugging. Before you start stepping
Create Hello World

through the source code, let's take a moment to notice several changes in the user interface:
Explore IntelliSense • The Integrated Terminal appears at the bottom of the source code editor. In the Debug Output tab,
Build helloworld.cpp you see output that indicates the debugger is up and running.
• The editor highlights the first statement in the main method. This is a breakpoint that the C++
extension automatically sets for you:
Set a watch
Reusing your C++

configuration

Developer Command
Prompt
Troubleshooting
Next steps
msvc&via=code)
• The Run view on the left shows debugging information. You'll see an example later in the tutorial.
Subscribe(/feed.xml) • At the top of the code editor, a debugging control panel appears. You can move this around the
Ask
(https://stackoverflow.com screen by grabbing the dots on the left side.
/questions/tagged
questions
/vscode)
Step through the code #
features/fwlink/?LinkID=533482) Now you're ready to start stepping through the code.
Report 1. Select the Step over icon in the debugging control panel until the for (const string& word :
/Microsoft/vscode
issues
/issues) msg) statement is highlighted.
Watch
/channel
videos
The Step Over command skip over all the internal function calls within the vector and string
classes that are invoked when the msg variable is created and initialized. Notice the change in the
Variables window on the left. In this case, the errors are expected because, although the variable
names for the loop are now visible to the debugger, the statement has not executed yet, so there is
nothing to read at this point. The contents of msg are visible, however, because that statement has
completed.
2. Press Step over again to advance to the next statement in this program (skipping over all the
internal code that is executed to initialize the loop). Now, the Variables window shows information
about the loop variables.
3. Press Step over again to execute the cout statement. Note As of the March 2019 version of the
extension, no output is displayed until the loop completes.
4. If you like, you can keep pressing Step over until all the words in the vector have been printed to the
console. But if you are curious, try pressing the Step Into button to step through source code in the
C++ standard library!
IN THIS ARTICLE
Prerequisites
Create Hello World
Set a watch
To return to your own code, one way is to keep pressing Step over. Another way is to set a
breakpoint in your code by switching to the helloworld.cpp tab in the code editor, putting the
Reusing your C++
insertion point somewhere on the cout statement inside the loop, and pressing F9 . A red dot
configuration
appears in the gutter on the left to indicate that a breakpoint has been set on this line.
Developer Command
Prompt
Troubleshooting
Next steps
Tweet//code.visualstudio.com/docs/cpp/config-msvc&ref_src=twsrc%5Etfw& Then press F5 to start execution from the current line in the standard library header. Execution will
link tw_p=tweetbutton&url=https://code.visualstudio.com/docs/cpp/config- break on cout . If you like, you can press F9 again to toggle off the breakpoint.
msvc&via=code)
Set a watch #
Ask
/questions/tagged
questions
/vscode)
Sometimes you might want to keep track of the value of a variable as your program executes. You can do
@code/fwlink/?LinkID=533687) this by setting a watch on the variable.
1. Place the insertion point inside the loop. In the Watch window, select the plus sign and in the text
box, type word , which is the name of the loop variable. Now view the Watch window as you step
Report
issues
/Microsoft/vscode through the loop.
/issues)
Watch
/channel
videos
2. Add another watch by adding this statement before the loop: int i = 0; . Then, inside the loop,
add this statement: ++i; . Now add a watch for i as you did in the previous step.
3. To quickly view the value of any variable while execution is paused on a breakpoint, you can hover
over it with the mouse pointer.
C/C++ configurations #
If you want more control over the C/C++ extension, you can create a c_cpp_properties.json file,
which will allow you to change settings such as the path to the compiler, include paths, C++ standard
(default is C++17), and more.
IN THIS ARTICLE
You can view the C/C++ configuration UI by running the command C/C++: Edit Configurations (UI) from
Prerequisites
the Command Palette ( Ctrl+Shift+P ).
Create Hello World
Set a watch
Reusing your C++

configuration

Developer Command
Prompt
Troubleshooting
Next steps
This opens
link tw_p=tweetbutton&url=https://code.visualstudio.com/docs/cpp/config- the C/C++ Configurations page. When you make changes here, VS Code writes them to a file
msvc&via=code)
called c_cpp_properties.json in the .vscode folder.
Ask
/questions/tagged
questions
/vscode)
Report
/Microsoft/vscode
issues
/issues)
Watch
/channel
videos
Visual Studio Code places these settings in .vscode\c_cpp_properties.json . If you open that file
directly, it should look something like this:
{
"configurations": [
{
"name": "Win32",
IN THIS ARTICLE
"includePath": ["${workspaceFolder}/**"],
Prerequisites "defines": ["_DEBUG", "UNICODE", "_UNICODE"],
"windowsSdkVersion": "10.0.18362.0",
Create Hello World
"compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/BuildTools/VC/Tool
Explore IntelliSense s/MSVC/14.24.28314/bin/Hostx64/x64/cl.exe",
"cStandard": "c11",
"cppStandard": "c++17",
Debug helloworld.cpp "intelliSenseMode": "msvc-x64"
}
],
Set a watch "version": 4
C/C++ configurations }
Reusing your C++

configuration You only need to add to the Include path array setting if your program includes header files that are not
in your workspace or in the standard library path.
Developer Command
Prompt
Troubleshooting Compiler path #

Next steps The compilerPath setting is an important setting in your configuration. The extension uses it to infer the
(https://twitter.com/intent/tweet?original_referer=https: path to the C++ standard library header files. When the extension knows where to find those files, it can
provide useful features like smart completions and Go to Definition navigation.
The C/C++ extension attempts to populate compilerPath with the default compiler location based on
msvc&via=code)
what it finds on your system. The extension looks in several common compiler locations.
(https://stackoverflow.com The compilerPath search order is:

Ask
/questions/tagged
questions
/vscode) • First check for the Microsoft Visual C++ compilerOpe
Follow (https://go.microsoft.com • Then look for g++ on Windows Subsystem for Linux (WSL)
• Then g++ for Mingw-w64.
features/fwlink/?LinkID=533482) If you have g++ or WSL installed, you might need to change compilerPath to match the preferred
Report compiler for your project. For Microsoft C++, the path should look something like this, depending on
/Microsoft/vscode
issues
/issues) which specific version you have installed: "C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools
(https://www.youtube.com /VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64/cl.exe".
Watch
/channel
videos
Reusing your C++ configuration #

VS Code is now configured to use the Microsoft C++ compiler. The configuration applies to the current
workspace. To reuse the configuration, just copy the JSON files to a .vscode folder in a new project
folder (workspace) and change the names of the source file(s) and executable as needed.
Run VS Code outside the Developer Command Prompt #

In certain circumstances, it isn't possible to run VS Code from Developer Command Prompt for Visual
Studio (for example, in Remote Development through SSH scenarios). In that case, you can automate
initialization of Developer Command Prompt for Visual Studio during the build using the following
tasks.json configuration:
{
"version": "2.0.0",
"windows": {
"options": {
IN THIS ARTICLE
"shell": {
Prerequisites "executable": "cmd.exe",
"args": [
Create Hello World
"/C",
Explore IntelliSense // The path to VsDevCmd.bat depends on the version of Visual Studio you have instal
led.
"\"C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/Tools/VsDe
Debug helloworld.cpp vCmd.bat\"",
"&&"
]
Set a watch }
C/C++ configurations }
},
Reusing your C++ "tasks": [
configuration
{
Run VS Code outside the "type": "shell",
Developer Command "label": "cl.exe build active file",
Prompt "command": "cl.exe",
"args": [
Troubleshooting
"/Zi",
Next steps "/EHsc",
"/Fe:",
(https://twitter.com/intent/tweet?original_referer=https: "${fileDirname}\\${fileBasenameNoExtension}.exe",
Tweet//code.visualstudio.com/docs/cpp/config-msvc&ref_src=twsrc%5Etfw& "${file}"
this text=Configure%20Visual%20Studio%20Code%20for%20Microsoft%20C++& ],
"problemMatcher": ["$msCompile"],
msvc&via=code)
"group": {
Subscribe(/feed.xml) "kind": "build",
(https://stackoverflow.com "isDefault": true
Ask }
/questions/tagged
questions }
/vscode)
]
}
features/fwlink/?LinkID=533482) Note: The path to VsDevCmd.bat might be different depending on the Visual Studio version or
Report installation path. You can find the path to VsDevCmd.bat by opening a Command Prompt and
/Microsoft/vscode
issues
/issues) running dir "\VsDevCmd*" /s .
Watch
/channel
videos
Troubleshooting #
The term 'cl.exe' is not recognized #

If you see the error "The term 'cl.exe' is not recognized as the name of a cmdlet, function, script file, or
operable program.", this usually means you are running VS Code outside of a Developer Command
Prompt for Visual Studio and VS Code doesn't know the path to the cl.exe compiler.
VS Code must either be started from the Developer Command Prompt for Visual Studio, or the task must
be configured to run outside a Developer Command Prompt.
You can always check that you are running VS Code in the context of the Developer Command Prompt by
opening a new Terminal ( Ctrl+Shift+` ) and typing 'cl' to verify cl.exe is available to VS Code.
fatal error C1034: assert.h: no include path set #

In this case, cl.exe is available to VS Code through the PATH environment variable, but VS Code still
needs to either be started from the Developer Command Prompt for Visual Studio, or be configured to
run outside the Developer Command Prompt. Otherwise, cl.exe does not have access to important
environment variables such as INCLUDE .
IN THIS ARTICLE
Prerequisites
Next steps #
Create Hello World
• Explore the VS Code User Guide (/docs/editor/codebasics).
• Review the Overview of the C++ extension (/docs/languages/cpp).
• Create a new workspace, copy your .vscode JSON files to it, adjust the necessary settings for the
new workspace path, program name, and so on, and start coding!
Set a watch
Reusing your C++ Was this documentation helpful?

configuration
Run VS Code outside the Yes No

Developer Command
Prompt
Troubleshooting
Next steps 8/19/2021
msvc&via=code)
Ask
/questions/tagged
questions
/vscode)
Report
/Microsoft/vscode
issues
/issues)
Watch
/channel
videos

Configure Visual Studio Code For Microsoft C++

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configure Visual Studio Code For Microsoft C++

Uploaded by

Copyright:

Available Formats

Version 1.63 (/updates) is now available! Read about the new features and fixes from November.

GET STARTED Debug helloworld.cpp

C++ Next steps

Intro Videos (/docs Prerequisites # (https://twitter.com/intent/tweet?original_referer=https:

Create Hello World

Step through the code

Reusing your C++

IN THIS ARTICLE creating new projects.

Step through the code

Set a watch Create Hello World #

Add hello world source code #

Debug helloworld.cpp for (const string& word : msg)

Create Hello World

Reusing your C++

Run VS Code outside the

Reusing your C++

Create Hello World

Troubleshooting Debug helloworld.cpp #

Create Hello World

Reusing your C++

Run VS Code outside the

Create Hello World

Step through the code

Step through the code

Reusing your C++

Run VS Code outside the

Reusing your C++

Troubleshooting Compiler path #

(https://stackoverflow.com The compilerPath search order is:

Reusing your C++ configuration #

Run VS Code outside the Developer Command Prompt #

The term 'cl.exe' is not recognized #

fatal error C1034: assert.h: no include path set #

Reusing your C++ Was this documentation helpful?

Run VS Code outside the Yes No

Next steps 8/19/2021

You might also like