Releases: microsoft/vscode-cpptools
1.22.3
Instructions
Install it via using the Extensions view in VS Code and choosing the option "Switch to Pre-Release Version" or download a vsix that matches your OS from the "Download" dropdown in the "Version History" tab section on the Marketplace website) and then use the Extensions: Install from VSIX...
command in VS Code (don't double-click the vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.67.0 or later (April, 2022).
- Windows 7+, macOS 10.12+, Linux (Ubuntu 16+, etc.).
Changes
Enhancement
- Add support for providing additional context information to Copilot Chat. PR #12685
- Currently, it requires
"C_Cpp.experimentalFeatures": "enabled"
and typing#cpp
in the chat.
- Currently, it requires
Bug Fixes
- Fix the compiler selection control not keeping the list in sync with contents of the textbox. #7427
- Fix a string localization issue. #7824
- Stop logging duplicate compiler path messages. #12445
- Fix some crashes with recursive includes. #12643
- Fix a rare crash on macOS related to
get_memory_usage
. #12667 - Fix an issue with 'Extract to Function' formatting. #12677
- Fix a potential deadlock in
process_paths
. #12690
1.22.2
Instructions
Install it via using the Extensions view in VS Code and choosing the option "Switch to Pre-Release Version" or download a vsix that matches your OS from the "Download" dropdown in the "Version History" tab section on the Marketplace website) and then use the Extensions: Install from VSIX...
command in VS Code (don't double-click the vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.67.0 or later (April, 2022).
- Windows 7+, macOS 10.12+, Linux (Ubuntu 16+, etc.).
Changes
Enhancement
- Remove the
C_Cpp.intelliSenseEngineFallback
setting. #12596
Bug Fix
- Fix a deadlock when doing "Find All References" and a file is deleted. #12656
1.22.1
Instructions
Install it via using the Extensions view in VS Code and choosing the option "Switch to Pre-Release Version" or download a vsix that matches your OS from the "Download" dropdown in the "Version History" tab section on the Marketplace website) and then use the Extensions: Install from VSIX...
command in VS Code (don't double-click the vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.67.0 or later (April, 2022).
- Windows 7+, macOS 10.12+, Linux (Ubuntu 16+, etc.).
Changes
Enhancement
- Add "Additional Tracked Settings" to
C/C++: Log Diagnostics
output. PR #12635
Bug Fixes
- Fix hover over static constexpr variables sometimes not working. #12284
- Fix completion not giving results in several scenarios. #12412
- Fix include completion showing results for deleted folders with recursive includes. #12636
- Fix the
/FU
flag not working for C++/CLI . #12641 - Fix some crashes with recursive includes. #12643
- Fix IntelliSense not working on Windows when
C_Cpp.caseSensitiveFileSupport
isenabled
. #12648 - Changes that might fix a crash with
translate_encoding_to_utf8
. #12652 - Fix a random crash during IntelliSense creation.
1.22.0
Instructions
Install it via using the Extensions view in VS Code and choosing the option "Switch to Pre-Release Version" or download a vsix that matches your OS from the "Download" dropdown in the "Version History" tab section on the Marketplace website) and then use the Extensions: Install from VSIX...
command in VS Code (don't double-click the vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.67.0 or later (April, 2022).
- Windows 7+, macOS 10.12+, Linux (Ubuntu 16+, etc.).
Changes
Performance Improvements
- Switch to an alternative implementation of recursive includes (that sends all the paths instead of only the "used" paths). #11780
- Performance improvement: Configuration is no longer blocked on tag parsing of all dependent headers.
- Configuration change: Recursive include paths now take precedence over system include paths (similar to compiler behavior and non-recursive includes). #11485
- Initialization performance improvements. #12030
- Improve the implementation of file buffers to reduce memory usage.
Enhancements
- Add modified
C_Cpp
settings to theC/C++: Log Diagnostics
output. #11700 - Change the default C/C++
"editor.stickyScroll.defaultModel"
to"foldingProviderModel"
. #12483 - Add better validation for settings. #12371
- Various IntelliSense parsing updates/fixes.
Bug Fixes
- Stop logging duplicate compiler path messages. #12445
- Fix an issue where a file is incorrectly processed as C instead of C++. #12466
- Fix include path ordering being incorrect if there is a duplicate. #12525
- Fix a WebAssembly "Out of Memory" error. #12529
- Fix an error message not being shown if the connection failed with remote attach debugging. #12547
- Thank you for the contribution. @MrStanislav0 (Stanislav)
- Fix
-I
not being used if-iquote
is also used for the same path. #12551 - Fix issues with relative paths on
nvcc
(CUDA) command lines not being handled correctly. #12553 - Fix a random crash when a child process is created. #12585
- Fix a crash on shutdown on macOS with a verbose logging level. #12567
- Fix some issues with recursive includes handling of symbolic links, multi-root, exclusion changes, and file/folder deletion.
- Fix unnecessary IntelliSense resetting when a new file or folder was created.
- Fix accumulation of stale signature help and completion requests.
- Fix some bugs with include completion.
1.21.6 (patch fix update)
Instructions
Install it via using the Extensions view in VS Code or download a vsix that matches your OS from Assets section below (or the "Download" dropdown in the "Version History" tab section on the Marketplace website) and then use the Extensions: Install from VSIX...
command in VS Code (don't double-click the vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.67.0 or later (April, 2022).
- Windows 7+, macOS 10.12+, Linux (Ubuntu 16+, etc.).
Changes
- Fix a cpptools-srv crash on shutdown. #12354
1.21.5 (patch fix update)
Instructions
Install it via using the Extensions view in VS Code or download a vsix that matches your OS from Assets section below (or the "Download" dropdown in the "Version History" tab section on the Marketplace website) and then use the Extensions: Install from VSIX...
command in VS Code (don't double-click the vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.67.0 or later (April, 2022).
- Windows 7+, macOS 10.12+, Linux (Ubuntu 16+, etc.).
Changes
Bug Fixes
1.21.4 (patch fix update)
Instructions
Install it via using the Extensions view in VS Code or download a vsix that matches your OS from Assets section below (or the "Download" dropdown in the "Version History" tab section on the Marketplace website) and then use the Extensions: Install from VSIX...
command in VS Code (don't double-click the vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.67.0 or later (April, 2022).
- Windows 7+, macOS 10.12+, Linux (Ubuntu 16+, etc.).
Changes
- Re-enable compatibility with VS Code 1.67.0 (instead of 1.82.0). #12507
1.21.3 (patch fix update)
Instructions
Install it via using the Extensions view in VS Code or download a vsix that matches your OS from Assets section below (or the "Download" dropdown in the "Version History" tab section on the Marketplace website) and then use the Extensions: Install from VSIX...
command in VS Code (don't double-click the vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.67.0 or later (April, 2022), but due to bug #12507, only 1.82.0 is supported until we release 1.21.4.
- Windows 7+, macOS 10.12+, Linux (Ubuntu 16+, etc.).
Changes
- Fix a crash on Linux ARM OS's. #12497
1.21.2
Instructions
Install it via using the Extensions view in VS Code or download a vsix that matches your OS from Assets section below (or the "Download" dropdown in the "Version History" tab section on the Marketplace website) and then use the Extensions: Install from VSIX...
command in VS Code (don't double-click the vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.67.0 or later (April, 2022).
- Windows 7+, macOS 10.12+, Linux (Ubuntu 16+, etc.).
Changes
Enhancements
- Add
see
andsa
to theC_Cpp.doxygen.sectionTags
setting. #12384 - Update the vcpkg header database. PR #12430
- Disable the pre-release prompt if the
extensions.ignoreRecommendations
setting istrue
. #12438 - Switch to an alternative workspace symbol search implementation (performance and results will be slightly different from previous versions).
- Various IntelliSense engine updates/fixes.
Bug Fixes
- Stop logging file watch events for excluded files. #11455
- Fix a crash if the Ryzen 3000 doesn't have updated drivers. #12201
- Fix handling of
-isystem
and-iquote
for IntelliSense configuration. #12207 - Fix doxygen comment generation when
/**
comments are used. #12249 - Fix a code analysis crash on Linux if the message is too long. #12285
- Fix relative paths in
compile_commands.json
to be relative to thecompile_commands.json
's directory. #12290 - Fix a tag parser performance regression. #12292
- Fix a regression with cl.exe system include path detection. #12293
- Fix code analysis, find all references, and rename from getting the wrong configuration for non-open files on the first run when using a configuration provider. #12313
- Fix handling of doxygen comment blocks with
*//*
in them. #12316 - Fix potential crashes during IntelliSense process shutdown. #12354
- Fix the language status not showing it's busy while the tag parser is initializing. #12403
- Fix the vcpkg code action not appearing for missing headers available via vcpkg. #12413
- Fix custom configurations sometimes not getting used. PR #12427
- Fix a code analysis error when using gcc 14. #12428
- Fix warning notification showing when
C_Cpp.getIncludes
is disabled. PR #12470 - Fix a cause of colorization, inactive regions, and inlay hints getting cleared when an update is pending.
- Update the default clang/gcc versions used for IntelliSense if an unknown version is found.
- Fix a cause of semantic tokens transiently being placed in the wrong location.
- Update clang-format and clang-tidy from 18.1.2 to 18.1.7 (for the bug fixes).
- Fix a potential deadlock when configured using compile commands.
1.21.1 (release candidate)
Instructions
Install it via using the Extensions view in VS Code and choosing the option "Switch to Pre-Release Version" or download a vsix that matches your OS from the "Download" dropdown in the "Version History" tab section on the Marketplace website) and then use the Extensions: Install from VSIX...
command in VS Code (don't double-click the vsix or another app like VS might try to open it incorrectly).
Requirements
- VS Code 1.67.0 or later (April, 2022).
- Platforms:
- Windows (7+): x64, arm64. (x86 is only available via the non-pre-release vsix on GitHub).
- Linux (Ubuntu 16+, etc.): x64, arm64, arm.
- macOS (10.12+): x64, arm64.
Changes
Enhancements
- Add
see
andsa
to theC_Cpp.doxygen.sectionTags
setting. #12384 - Update the vcpkg header database. PR #12430
- Disable the pre-release prompt if the
extensions.ignoreRecommendations
setting istrue
. #12438 - Switch to an alternative workspace symbol search implementation (performance and results will be slightly different from previous versions).
- Various IntelliSense engine updates/fixes.
Bug Fixes
- Fix a crash if the Ryzen 3000 doesn't have updated drivers. #12201
- Fix relative paths in
compile_commands.json
to be relative to thecompile_commands.json
's directory. #12290 - Fix a tag parser performance regression. #12292
- Fix code analysis, find all references, and rename from getting the wrong configuration for non-open files on the first run when using a configuration provider. #12313
- Fix potential crashes. #12354
- Fix the language status not showing it's busy while the tag parser is initializing. #12403
- Fix the vcpkg code action not appearing for missing headers available via vcpkg. #12413
- Fix custom configurations sometimes not getting used. PR #12427
- Fix a code analysis error when using gcc 14. #12428
- Fix a cause of colorization, inactive regions, and inlay hints getting cleared when an update is pending.
- Fix a cause of semantic tokens transiently being placed in the wrong location.
- Fix a potential deadlock when configured using compile commands.