I need some help as a newcomer to the SDK.
I have opened the sample solution (\build\win\prj\SDKSamples.sln) in VisualStudio 2019 in the current SDK (plugin_sdk_050).
I can compile the solution (probably because of the PreCompiled headers) - but in the IDE all "#Includes" are shown as not loadable. They cannot be found.
Did I miss any hint in the docs? Do I have to set some environment variable?
Thanks a lot in advance,
Below is a screenshot of my "VC++ Directories", where you'll need to replace "..\plugin_sdk_126.96.36.199\" with the path where your SDK is installed.
Very best regards,
I was hoping there was a more elegant "special" way than adding each directory individually.... 😉
You did not miss anything, if the plugin compiles fine then ignore the red wavy lines the IDE shows, the intellisense of VS does not work properly with InDesign plugin projects. I quote the following from the SDK guides
IntelliSense has never worked very well for InDesign code, and you may find that IntelliSense red squiggles appear under nearly every InDesign type or API, despite your project compiling successfully.
To disable the squiggles:
Thanks for this hint.
But in my case it seems that it's not only a issue with the "Squiggles". If I try to open the include file via the context menu Visual Studio is unable to find the header file. And yes - I'm able to build the projekt 😉
In such a case did you try what Oliver mentioned? That should probably fix it. However, I would like to ask if you did move around the project file shipped with the SDK? The project is set mostly with relative paths so moving around the projects causes lots of headaches to fix.
Yes, adding each directory like Olivier mentioned helped me. The squiggles are gone.
No - I did not moved the files around. It's just extracted the zip to c:\plugin_sdk_050
Just one more info: it seems the the build process is using all those *.rsp files with all the necessary include directories in the projects. I think that this is the reason why I can build the addins.
But it seems that IntelliSense did not use these definition files...