- This topic has 3 replies, 2 voices, and was last updated 6 years, 3 months ago by
.
-
Posts
-
Hi, using ‘Visual Studio 2017 Pro’ with ‘VisualGDB’, it appears that after having installed some extensions like ‘Editor Guidelines’ ( https://marketplace.visualstudio.com/items?itemName=PaulHarrington.EditorGuidelines ) or ‘Viasfora’ ( https://marketplace.visualstudio.com/items?itemName=TomasRestrepo.Viasfora ) they do not works until I open a file into a regular ‘Win32’ project. Once done at least once, it works in the ‘VisualGDB’ projects of the same solution.
Any way to get them working like expected ?
Hi,
This likely happens because those extensions are specifically looking for the regular Visual C++ project backend. If you are using Clang IntelliSense, it completely replaces the regular C++ IntelliSense, so extensions that are not aware of the Clang IntelliSense won’t find it.
You could disable Clang IntelliSense via VisualGDB Project Properties (or via a switch on the Clang IntelliSense Diagnostics Console window), however this would reduce the quality of the code completion results, as the Clang IntelliSense is specifically designed to work the best with GCC-specific code.
- You must be logged in to reply to this topic.