Following the roll out of the Windows 10 Insider build 16237 to the Fast Rings last week, Microsoft released yesterday the Windows 10 SDK Preview Build 16232 that developers can now use with the preview build 16232 or greater (this same build also rolled out to the Slow Ring a couple of days ago). Just like the latest preview build of the SDK, the latest version is only supported by Visual Studio 2017 and greater.
There are some API additions and removals on this later build, but developers should also be aware of two known issues and one breaking change:
- 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.
- 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.
You can download the new Preview DSK from the developer section of Microsoft’s Windows Insider website, and we invite you to read the full blog post to get more details about all the bug fixes and API changes.