Last week, Microsoft released Windows 10 for PCs build 16232 to the Slow ring, which was the first Fall Creators Update preview for Slow ring users. Today, the firm published new ISO images, and now, the SDK Preview for the build is available.
The SDK Preview is only officially supported on Visual Studio 2017, and while you can install it in a production environment, your app must be targeted at the Creators Update or earlier in order to submit it to the Windows Store. There are a few known issues to be aware of:
Designer fails to render: When viewing the XAML in the Designer Window in Visual Studio, the controls fail to render. This can be resolved by using Visual Studio 2017.3 Preview.
Compilation fails on non-Windows 10 platforms
When building apps on previous platforms, you may get a build error:
C:\program files (x86)\Windows Kits\10\bin\10.0.16232.0\x86\genxbf.dll:C:\program files (x860\Windows Kits\10\bin\10.0.16232.0\x86\genxbf.dll(0,0): Error WMC0621: Cannot resolve ‘GenXbf.dll’ under path ‘C:\program files (x860\Windows Kits\10\bin\10.0.16232.0\x86\genxbf.dll’. Please install the latest version of the Windows 10 Software Development Kit.
Process ‘msbuild.exe’ exited with code ‘1’.
This will occur if the minimum target platform version is set to 10.0.16225.0. To work around this, right click on your project file and choose properties or open your project file in your favorite editor, and change the version to a previous released SDK. For example:
WRL projects fail to compile with MIDLRT error: When building my WRL project that contains a WinRT Component, the project no longer compiles. I get the following errors:
midlrt : command line error MIDL1012: [msg]argument illegal for switch / [context]ns_prefix
midlrt : command line error MIDL1000: [msg]missing source-file name
And there's one item that's listed as a breaking change:
ecmangen.exe removal from the SDK: Ecmangen.exe will no longer ship with the Windows SDK. Developers who rely on ecmangen for event manifest creation are advised to install the Windows Creators Edition of the SDK to obtain the file. Developers may also use notepad or other XML editor of choice for manifest creation. A schema file is available on MSDN to aid in manifest creation, for tools that support it.
There are also a ton of API changes, which you can check out in the announcement. You can download the SDK Preview from Microsoft here, but you'll need to be signed into a Microsoft account that's enrolled in the Insider Program.