Strange behavior of Visual Studio Community 2022 17.3.6

[eyalamir]

Hey @oli1 and the rest of the JUCE team:

This issue will be fixed by adding explicit includes to the JUCE modules (without changing the unity build format).

We’ve discussed that here:

Adding Visual Studio Code code completion

Most of it would be the same. If you look at my example, many of the stuff in the module header are just copied to another header, like juce_osc_common.h and that includes all the external native headers in a very copy-paste way, as that part shouldn’t change.

and here:

Intellisense broken for JUCE cpp files in solutions

I have a memory like a colander - we have indeed had this conversation before, sorry!

And I’ve also attached an example on how to do that in the juce_osc module. This would have the advantage of also fixing intellisense in VS Code and other text editors that can’t parse through the build system.

Would be great if this (non breaking!) change could be applied. It’s slightly tedious work but shouldn’t take more than a few hours for the entire library.