pablo-msft

Nice. I can use that. That script is not documented anywhere, and the Windows documentation specifically does not make note of VS2022.

@latitb I think this can be retitled, since VS2022 can be used, but should not be closed. I acknowledge that build issues are out of support scope, due to consumers...

If I create a build.*.props file, and I put `CONFIG_CUSTOM_H="filedoesnotexist"` in it, then the result is the same - successful build, no warnings about this. ``` %(PreprocessorDefinitions);CONFIG_CUSTOM_H="filedoesnotexist" ```