Problems with Projucer and VS2017 community edition

[alatar]

Well, personally I am not using the LiveBuild feature.
Instead I open the JUCE project directly in Visual Studio 2017. You know that you can do that, right?
But if you want to test the live build, you can check out the following forum thread:

Win Live Build?

Hmm, strange. I’ve installed the latest Windows 10 SDK supporting VS2015 (10.0.17134.0) at the default location (c:\Program Files (x86)\Windows Kits\10) and I get the ‘memory’ file not found error. I changed the Windows Target Platform to 10.0.17134.0 in both the Live build tab and the VS2015 exporter tab. When looking in the sub folders of c:\Program Files (x86)\Windows Kits\10\Include\10.0.17134.0\ there is no memory file (a memory.h file exists but that’s not very helpful). I tried adding C…