Intellisense (Github Copilot)

[hikingDev]

Hello,

I came across a discussion in another forum thread which mentioned that to use VisualGDB with GitHub Copilot, one must select the “Regular VC++ IntelliSense” option. However, when I attempted to do this, the option was unavailable (greyed out) with a note stating: “This project type only supports the Clang IntelliSense engine”. For context, I’m working on an ESP32 project. Any insights or solutions would be appreciated.

Thank you

 

Attachments:

You must be logged in to view attached files.

[support]

Hi,

Based on what we tested, CoPilot works just fine with the Clang IntelliSense engine. It shows a different language type – C/C++ (VisualGDB) instead of just C/C++, but otherwise works the same:

Also it appears to only use the current source file contents for figuring out the completion. You can try creating a new Win32 Console Application, adding the ESP32 source file there, and it will generate the same suggestions regardless of the unresolved headers and other errors. Note that the suggestions are very sensitive to the exact location in the file – generating a body for the same function defined at the beginning, end, or somewhere in the middle yielded completely different results in our tests.

As for why the original C/C++ engine is disabled, it only works with the project types managed by Visual Studio itself (i.e. native VC++). ESP32 projects are managed by VisualGDB – they don’t use the .vcxproj files and instead dynamically show the exact project structure reported by the ESP-IDF build tools. Regular Visual Studio IntelliSense doesn’t know how to work with such dynamic projects, hence we only allow selecting it for the vcxproj-based projects where it can work.

Attachments:

You must be logged in to view attached files.

[Author]

Posts