24 May, 2017 ()
Windows UWP export update, some more additions, and even more bug fixes
There was an issue in r30 that caused problems previewing certain projects, so we've got r31 hot on its heels to try to make sure everything is working smoothly. There's still a boat load of other bug fixes, as we're working our way through the many reports we've had so far.
One of the main additions this build is that the Windows UWP exporter now prompts for the Windows 10 SDK version when exporting. You only need to enter this once, since it remembers the setting. However this value needs to be set to the Windows 10 SDK version you have installed for the exported project to open in Visual Studio 2017. You can usually spot it in the Visual Studio installer, or see the Windows 10 SDK installation version in Add/Remove Programs (although it appears for Visual Studio the last number should always be 0). Typically the Windows 10 SDK version looks a bit like a Windows 10 build number, e.g. 10.0.14393.0. We can't automatically detect this or tell Visual Studio to use any kind of default, you have to provide the correct value. However this also has the bonus that even in Visual Studio 2015, setting the right value means you no longer have to adjust the Visual Studio target SDK property for it to work, which makes it a bit quicker and easier to get going.
Email Me New Releases
Don't miss out on the latest and greatest new features in Construct 3.
Create an Account