Short answer: Yes, you need to rename .cpp files to c, so you can write C: https://msdn.microsoft.com/en-us/library/bb384838.aspx?f=255&MSPPError=-2147217396

From the link above:

By default, the Visual C++ compiler treats all files that end in .c as C source code, and all files that end in .cpp as C++ source code. To force the compiler to treat all files as C regardless of file name extension, use the /Tc compiler option.

That being said, I do not recommend learning C language in Visual Studio, why VS? It does have lots of features you are not going to use while learning C

Thanks for reaching out. Here’s a breakdown for their roles:

1.      Settings.json

·         Used by the C/C++ extension in VS code.

·         The setting “C_Cpp.default.compilerPath” (or “C_Cpp.default.intelliSenseMode”) tells the IntelliSense engine which compiler to reference.

·         This helps VS Code provide code completion, error squiggles, and IntelliSense consistent with the compiler you’re using.

·         It does not actually compile or run the code it’s mainly for editing experience.

2.      Tasks.json

·         Defines how your code is built when you run Ctrl+Shift+B(build task).

·         Specifies which compiler executable (e.g., gcc, clang, cl.exe) to call, along with arguments.

3.      Launch.json

·         Defines how your program is debugged.

·         Referring to the compiled binary(output from tasks.json) and configures debugger settings.

·         It does not directly specify the compiler path but indirectly depend on the build task that used the compiler.

How the compiler path is determined automatically

·         When you install the C / C++ extension, VS code tries to detect available compilers (gcc, clang, cl.exe) from your system PATH.

·         The first detected compiler may be auto-filled in tasks.json and launch.json.

·         If multiple compilers are found, you can configure “C_Cpp.default.compilerPath” in settings.json to guide the IntelliSense and then manually generate/update tasks via “C/C++: edit configurations(UI)”.

Prompting for compiler each time

·         Remove

“C_Cpp.default.compilerPtah” from settings.json, so VS Code asks when IntelliSense needs it.

·         Or define multiple tasks in

Tasks.json(e.g., one for GCC, one for Clag), then choose which task to run using “Run Build Task”.

·         Use CMake tools extension if you want automatic multi-compiler management.

So in short:

Settings.json -> IntelliSense compiler reference

Tasks.json -> Actual compilation task

Launch.json -> Debugging setup, tied to the build task

You can also refer to these sites:

·         C++ extension settings reference

·         Configure C/C++ IntelliSense

·         Using C++ on Linux in VS Code

·         Configure VS Code for Microsoft C++

Let me know if you need any further help with this. We'll be happy to assist.

If you find this helpful, please mark this as answered.

You can use C/C++ for Visual Studio Code as it provides code editing, navigation, and debugging support for C and C++ code.

Unless you are sure that you already have a compiler installed, make sure to install a C/C++ compiler and debugger and check the documentation for more instructions!

Popular C++ compilers are:

• GCC on Linux
• Mingw-w64 on Windows
• Microsoft C++ compiler on Windows
• Clang for XCode on macOS

To run your code, and unless you want to go through the hassle of manual configuration, you can use Code Runner

To run code:

• use shortcut Ctrl+Alt+N
• or press F1 and then select/type Run Code,
• or right click the Text Editor and then click Run Code in editor context menu
• or click Run Code button in editor title menu
• or click Run Code button in context menu of file explorer

To stop the running code:

• use shortcut Ctrl+Alt+M
• or press F1 and then select/type Stop Code Run
• or right click the Output Channel and then click Stop Code Run in context menu

You will also find more detailed instructions through the referenced links!

Caution

A friendly reminder: The following tutorial is for Linux user instead of Windows

Tutorial

If you want to debug your c++ code with GDB

You can read this ( Debugging your code ) article from Visual Studio Code official website.

Step 1: Compilation

You need to set up task.json for compilation of your cpp file

or simply type in the following command in the command window

g++ -g file.cpp -o file.exe

to generate a debuggable .exe file

Step 2: Set up the launch.json file

To enable debugging, you will need to generate a launch.json file

follow the launch.json example or google others

Step 3: Press (Ctrl+F5) to start compiling

this launch.json file will launch the configuration when you press the shortcut (Ctrl+F5)

Enjoy it!

ps. For those who want to set up tasks.json, you can read this from vscode official (-> TypeScript Hello World)

MSYS2 comes with a package manager pacman that you should use to install any components you need.

In your case, open the MSYS2 shell (by running mingw64.exe) and run the following commands:

pacman -Syu --noconfirm 
pacman -S mingw-w64-x86_64-toolchain

The first command will tell the package manager to update it's database, the second command will get the MinGW-w64 64-bit GCC compiler.

If you don't really need MSYS2 (e.g. because you dan't plan to use the MSYS2 shell) you could also consider getting a standalone MinGW-w64 build from https://winlibs.com/