These steps will allow you to debug the TypeScript code that is part of the Microsoft CppTools extension for Visual Studio Code.

Prerequisite steps:

* Clone[this](https://github.com/Microsoft/vscode-cpptools) repository.

* Install[npm](https://nodejs.org).

* From a command line, run the following commands from the**Extension** folder in the root of the repository:

*`npm install -g vsce` will install`vsce` globally to create the vsix package.

*`npm install` will install the dependencies needed to build the extension.

* Set an environment variable`CPPTOOLS_DEV=1`.

* This enables the local developer workflow, copying dependencies from the**node_modules** folder.

* Open the**Extension** folder in Visual Studio Code and F5.

* Read the[contributing guidelines](https://github.com/Microsoft/vscode-cpptools/blob/master/CONTRIBUTING.md).

These steps will allow you to debug the TypeScript code that is part of the Microsoft CppTools extension for Visual Studio Code.

Prerequisite steps:

* Clone[this](https://github.com/Microsoft/vscode-cpptools) repository.

* Install[npm](https://nodejs.org).

* From a command line, run the following commands from the**Extension** folder in the root of the repository:

*`npm install` will install the dependencies needed to build the extension.

***(optional)**`npm install -g vsce` will install`vsce` globally to create a VSIX package that you can install.

***(optional)** Set an environment variable`CPPTOOLS_DEV=1`.

* This enables the local developer workflow when testing the debugger, copying dependencies from the**node_modules** folder. Testing the language server does not require this step.

* Open the**Extension** folder in Visual Studio Code and press F5. This will launch a VS Code Extension Host window and activate the TypeScript debugger. You can set breakpoints on the extension source code and debug your scenario.

* Fix`Go to Definition` for code scoped with an aliased namespace.[#387](https://github.com/Microsoft/vscode-cpptools/issues/387)

* Fix incorrect IntelliSense errors with template template-arguments.[#1014](https://github.com/Microsoft/vscode-cpptools/issues/1014)

* Fix crash when using designated initializer lists.[#1440](https://github.com/Microsoft/vscode-cpptools/issues/1440)

* Add`windowsSdkVersion` to`c_cpp_properties.json`.[#1585](https://github.com/Microsoft/vscode-cpptools/issues/1585)

* Add`${vcpkgRoot}` variable.[#1817](https://github.com/Microsoft/vscode-cpptools/issues/1817)

* Fix dangling IntelliSense processes.[#2075](https://github.com/Microsoft/vscode-cpptools/issues/2075),[#2169](https://github.com/Microsoft/vscode-cpptools/issues/2169)

* Fix incorrect IntelliSense errors when class template argument deduction is used.[#2101](https://github.com/Microsoft/vscode-cpptools/issues/2101)

* Skip automatic parsing of source files in Mac system framework paths.[#2156](https://github.com/Microsoft/vscode-cpptools/issues/2156)

* Fix`Edit Configurations...` not working after`c_cpp_properties.json` is deleted.[#2214](https://github.com/Microsoft/vscode-cpptools/issues/2214)

* Fix indexing of the entire root drive on Windows when no is folder open.[#2216](https://github.com/Microsoft/vscode-cpptools/issues/2216)

* Disable the config provider message for headers outside the workspace and when debugging.[#2221](https://github.com/Microsoft/vscode-cpptools/issues/2221)

* Add`Change Configuration Provider...` command.[#2224](https://github.com/Microsoft/vscode-cpptools/issues/2224)

* Fix out-of-memory crash with`#include` code actions when no folder is open.[#2225](https://github.com/Microsoft/vscode-cpptools/issues/2225)

* Fix`intelliSenseMode` with custom config providers on Windows.[#2228](https://github.com/Microsoft/vscode-cpptools/issues/2228)

* Fix formatting not working on Windows if the VC++ 2015 redist isn't installed.[#2232](https://github.com/Microsoft/vscode-cpptools/issues/2232)

* Fix variables not resolving in`macFrameworkPath`.[#2234](https://github.com/Microsoft/vscode-cpptools/issues/2234)

* Fix`Go to Definition` not working for macros followed by`.` or`->`.[#2245](https://github.com/Microsoft/vscode-cpptools/issues/2245)

* Fix`#include` autocomplete with Mac framework headers.[#2251](https://github.com/Microsoft/vscode-cpptools/issues/2251)

* Fix for debugging to support empty arguments for debuggee.[#2258](https://github.com/Microsoft/vscode-cpptools/issues/2258)

* Fix`Go to Definition` bug (missing symbols outside the workspace).[#2281](https://github.com/Microsoft/vscode-cpptools/issues/2281)

* Add a setting to silence configuration provider warnings.[#2292](https://github.com/Microsoft/vscode-cpptools/issues/2292)

* Fix for debugging async Visual C++ causing debugger to hang.

* Fix`main` snippet.

* Fix the database icon getting stuck with recursive includes.[#2104](https://github.com/Microsoft/vscode-cpptools/issues/2104)

* Fix the red flame appearing late with recursive includes.[#2105](https://github.com/Microsoft/vscode-cpptools/issues/2105)

* Reference highlighting is now provided by the extension for both IntelliSense engines.

* Parameter help is now provided by both IntelliSense engines.

* Light bulbs (code actions) for #include errors now suggest potential paths to add to the`includePath` based on a recursive search of the`browse.path`.[#846](https://github.com/Microsoft/vscode-cpptools/issues/846)

* Light bulbs (code actions) for`#include` errors now suggest potential paths to add to the`includePath` based on a recursive search of the`browse.path`.[#846](https://github.com/Microsoft/vscode-cpptools/issues/846)

* Browse database now removes old symbols when`browse.path` changes.[#262](https://github.com/Microsoft/vscode-cpptools/issues/262)

* Add`*` on new lines after a multiline comment with`/**` is started.[#579](https://github.com/Microsoft/vscode-cpptools/issues/579)

* Fix`Go to Definition`, completion, and parameter hints for partially scoped members.[#635](https://github.com/Microsoft/vscode-cpptools/issues/635)

"type":"string"

}

},

"windowsSdkVersion": {

"description":"Version of the Windows SDK include path to use on Windows, e.g. '10.0.17134.0'.",

"type":"string",

"pattern":"^\\d{2}\\.\\d{1}\\.\\d{5}\\.\\d{1}$|^8\\.1$"

},

"defines": {

"description":"A list of preprocessor definitions for the IntelliSense engine to use while parsing files. Optionally, use = to set a value, e.g. VERSION=1.",

"type":"array",