IntelliSense errors with importing a module on Windows with cl.exe

    Ok, some progress:

I've created a new simpler project with one module but this time, I've created from Visual Studio 2022 Community CMake project wizard.

This time Visual Studio has no problem in finding the module (you must compile it twice for it to work properly - because the first time it generates the ifc files):

VSCode still can't see it:

The CMake project uses presets when created with VS wizards.

In both I can compile, run, and debug normally.

And if I force the /ifcSearchDir into CMakeLists.txt VSCode gives me the edgm error (VS does see the modules and finds the ifc files without setting this manually in the CMakeLists.txt). I noticed that .command files were generated in the build destination, and they have all the compilers parameters that are necessary to compile each file. My guess is that VS is using it to correctly generate the Intellisense and find everything.

Originally posted by @Bigous in https://github.com/microsoft/vscode-cpptools/issues/6302#issuecomment-1269190650

Reproduce the module-import IntelliSense failure in the linked Visual Studio 2022 CMake project, using its presets and cl.exe. Compare the generated .command files and CMakeLists.txt, including /ifcSearchDir, to determine how compiler parameters are discovered. Done means VS Code finds the generated .ifc module files without manual configuration and no longer reports the edgm error.