Windows 10: CANNOT FIND C/C++ EXTENSION ON VISUAL STUDIO

Blackpinkinyourarea21 · Aug 4, 2019

i have tried a various keyword to in the search but I coudnt find c/c++ extension on VISUAL STUDIO

helppppp pleassseeeeee

:)

Brink · Aug 4, 2019

December Update for the Visual Studio Code C/C++ extension

At //Build this year we launched the C/C++ extension for Visual Studio Code. Keeping with the monthly release cadence and goal to continuously respond to your feedback, this December update introduces the following features:

Debugger visualizations by default with Pretty Printing for GDB users

Ability to map source files during debugging

If you haven’t already provided us feedback, please take this quick survey to help shape this extension for your needs. The original blog post has already been updated with these new feature additions. Let’s learn more about each one of them now!
Click to expand...

Read more: December Update for the Visual Studio Code C/C++ extension | Visual C++ Team Blog

Brink · Aug 4, 2019

Visual Studio Code C/C++ extension March 2018 update

Today we are excited to announce the March 2018 update to the Visual Studio Code C/C++ extension! This update includes improved auto-complete for local and global scopes and a simplified configuration process for system includes and defines, enabling a better out-of-box IntelliSense experience. You can find the full list of changes in the release notes.

We’d like to thank everyone who tried our Insiders builds earlier this month and sent us feedback! Fixes for the issues you reported and feature suggestions you told us about helped shape the final release the way it is today. If you are not yet an insider but are interested, we’d love for you to join the VS Code C/C++ Insiders program.

Auto-complete for local and global scopes

While this feature is not completely new, IntelliSense now provides a semantic-aware list of auto-complete suggestions when you type in local and global variables and functions. Compared with the previous approach, the new auto-complete experience gives you a shorter and more relevant list of suggestions, making it easier to write C/C++ code.

System includes and defines automatically retrieved from the compiler

IntelliSense now automatically retrieves system includes and defines from GCC/Clang-based compilers, eliminating the need for manual configuration in the “includePath” and “defines” settings. On Mac and Linux, the IntelliSense engine automatically selects a compiler as the default by searching for the installed compilers on the system. You can check which compiler is being used in the new “compilerPath” setting in the c_cpp_properties.json file, and change the value if needed. The “compilerPath” setting also accepts compiler arguments that affect the system defines returned.

In addition, the new “cStandard” and “cppStandard” settings allow setting language standards explicitly for IntelliSense.

Force IntelliSense to process arbitrary headers

If you wish IntelliSense to process headers that are not explicitly listed in #include statements, you can now use the new “forcedInclude” setting to specify them. The IntelliSense engine will first process these headers before it looks at #includes.

Tell us what you think

Download the C/C++ extension for Visual Studio Code, try it out, and let us know what you think. File issues and suggestions on GitHub. If you haven’t already provided us feedback, please take this quick survey to help shape this extension for your needs. You can also find us on Twitter (@VisualC).
Click to expand...

Source: Visual Studio Code C/C++ extension March 2018 update | Visual C++ Team Blog

Brink · Aug 4, 2019

Visual Studio Code C/C++ extension May 2017 Update

Earlier this month, the C/C++ extension for Visual Studio Code hit another exciting milestone – it has been installed over 1.5 million times since it first shipped in March last year! Thanks to everyone who has sent us feedback to help us make it this far. We will continue to make improvements to the extension based on your feedback.

Today we are shipping the May 2017 update to the C/C++ extension for Visual Studio Code. In addition to several bug fixes, this update added auto-completion for keywords, enables error squiggles and quick info which shipped in April as experimental features, and improves the experience to configure debugger settings, making it much easier to get started with debugging C/C++ code in VS Code.

The original blog post, which provides an overview of this extension, has been updated with these changes. If you have this extension installed already, Visual Studio Code sends a notification for the update and installs the update for you automatically. If you haven’t installed it before, download the C/C++ extension for Visual Studio Code to try it out.

Improved experience to debugger configuration

One of the common pieces of user feedback we’ve heard constantly is that configuring the debugger is challenging. In this update, we simplified the default configuration in the debugger configuration file (launch.json) to make it relevant to the OS that you’re debugging on, and also now provides snippets to make it easier to add additional configurations.

After installing the May 2017 release of the extension, VS Code will prompt to be reloaded for the new configuration experience to take effect. This will only happen the first time the extension is installed/updated and activated.

Default configuration

To start debugging, first click on the Debug button on the left side of the VSCode window, then click on the gear icon at the top and type in “C++” in the Command Palette to find the debugger options.

For example, selecting the C++ (GDB/LLDB) option on a Windows machine will create a new launch.json file, if it doesn’t exist, with the following default configuration:

Note that the newly-created launch.json file is much simpler and shorter than it was before. It now only contains one configuration to help you launch and debug your current application on the OS that VS Code is running on. The only things that you need to fill in here are:

miDebuggerPath: replace the value with the path to the GDB debugger on your machine

program: replace the value with the path to your program executable

args: any arguments you want to pass to your program

Once these are completed, you can hit the green arrow button or press F5 to start debugging.

Add additional configurations

If you want to do other types of debugging, clicking the blue “Add Configuration…” button within the launch.json file will allow you to add other configurations. This button brings up a snippet list which shows the configurations that are applicable to the host OS. For example, the list on Windows (the first screenshot) and the list on Linux (the second screenshot) look like the following:

Configurations available on Windows:

Configurations available on Linux:

Selecting a snippet from the list will add a new configuration in your launch.json file.

Tell us what you think

Download the C/C++ extension for Visual Studio Code, try it out and let us know what you think. File issues and suggestions on GitHub. If you haven’t already provided us feedback, please take this quick survey to help shape this extension for your needs.
Click to expand...

Source: Visual Studio Code C/C++ extension May 2017 Update | Visual C++ Team Blog

Windows 10: CANNOT FIND C/C++ EXTENSION ON VISUAL STUDIO

CANNOT FIND C/C++ EXTENSION ON VISUAL STUDIO

CANNOT FIND C/C++ EXTENSION ON VISUAL STUDIO

CANNOT FIND C/C++ EXTENSION ON VISUAL STUDIO

CANNOT FIND C/C++ EXTENSION ON VISUAL STUDIO - Similar Threads - CANNOT FIND C++

C/C++ extension doesn't show up in Visual Studio Code extension manager search.

microsoft visual studio c++

Visual Studio Code C/C++ extension June 2018 Update

Visual Studio Code C/C++ extension July 2017 Update

Visual Studio Code C/C++ extension May 2017 Update

Visual Studio Code C/C++ extension April 2017 Update

Visual Studio Code C/C++ extension March 2018 update

December Update for the Visual Studio Code C/C++ extension

Visual Studio Code C/C++ extension August 2017 Update