Open wmmc88 opened 1 year ago
As of now I don't think we're going to add this. The workaround is to add alternative build files, such as CMakeLists.txt (or somehow generate a compile_commands.json or configure some other way).
That's a shame đ I'm working with several large projects and it isn't feasible for me to create cmakelists manually for all iof them. I did look into generating a compile_commands json database but for msbuild, there's no 1st party support and I could not find any 3rd party support either.
This feature request is being closed due to insufficient upvotes. Please leave a đ-upvote or đ-downvote reaction on the issue to help us prioritize it. When enough upvotes are received, this issue will be eligible for our backlog.
This feature request has received enough votes to be added to our backlog.
Environment
I'm trying to use vscode with C++ projects originally created in Visual Studio. These projects are configured via
.sln
and.vcxproj
files. The code navigation is very limited. I cannot "go to definition" or "go to delcaration" when those definitions and declarations are in other files. I believe this is because cpptools doesn't parsevcxproj
andsln
files in the same way that it parsescompile_commands.json
databases or other similar files.Bug Summary and Steps to Reproduce
Bug Summary: "go to definition" or "go to delcaration" does not work when those definitions and declarations are in other files. This occurs in projects based on
.vcxproj
filesSteps to reproduce:
Expected behavior
Ability to fully use all features that rely on cpptools knowing how the project is compiled.
Code sample and Logs