Windows 10 SDK Preview Build 18317 currently available!

Today, we released a brand new Windows 10 Preview Build of the SDK to be used in conjunction with Windows 10 Insider Preview (Build 18317 or greater). The Preview SDK Build 18317 contains bug fixes and under development changes towards the API surface area.

The Preview SDK obtainable from developer section on Windows Insider.

For feedback and updates to the known issues, please visit the developer forum. For new developer feature requests, head over to our Windows Platform UserVoice.
Things to note:

This build works in conjunction with previously released SDKs and Visual Studio 2017. You can install this SDK but still also continue to submit your apps that concentrate on Windows 10 build 1809 or earlier towards the Microsoft Store.
The Windows SDK will now formally simply be based on Visual Studio 2017 and greater. You are able to download the Visual Studio 2017 here.
This build of the Windows SDK will install ONLY on Windows 10 Insider Preview builds.
In to help with script access towards the SDK, the ISO will also be able to be accessed through the following URL: https://go.microsoft.com/fwlink/?prd=11966&pver=1.0&plcid=0x409&clcid=0x409&ar=Flight&sar=Sdsurl&o1=18317 when the static URL is published.

Tools Updates
Message Compiler (mc.exe)

The “-mof” switch (to generate XP-compatible ETW helpers) is considered to be deprecated and will also be removed inside a future form of mc.exe. Removing this switch will cause the generated ETW helpers to expect Vista or later.
The “-A” switch (to create .BIN files using ANSI encoding instead of Unicode) is regarded as deprecated and will be removed inside a future form of mc.exe. Removing this switch will cause the generated .BIN files to make use of Unicode string encoding.
The behavior from the “-A” switch has changed. Just before Windows 1607 Anniversary Update SDK, while using the -A switch, BIN files were encoded while using build system’s ANSI code page. Within the Windows 1607 Anniversary Update SDK, mc.exe’s behavior was inadvertently changed to encode BIN files while using build system’s OEM code page. Within the 19H1 SDK, mc.exe’s previous behavior has been restored and it now encodes BIN files using the build system’s ANSI code page. Note that the -A switch is deprecated, as ANSI-encoded BIN files don’t provide a consistent consumer experience in multi-lingual systems.

Breaking Changes
Switch to effect graph from the AcrylicBrush

In this Preview SDK, we’ll be adding a mix mode towards the effect graph of the AcrylicBrush called Luminosity. This blend mode will ensure that shadows do not appear behind acrylic surfaces without a cutout. We’ll also be exposing a LuminosityBlendOpacity API available for tweaking that enables for additional AcrylicBrush customization.

By default, for those that have not specified any LuminosityBlendOpacity on their own AcrylicBrushes, we’ve implemented some logic to make sure that the Acrylic will appear as similar as it can to current 1809 acrylics. Please be aware that we’ll be updating our default brushes to take into account this recipe change.
TraceLoggingProvider.h / TraceLoggingWrite

Events generated by TraceLoggingProvider.h (e.g. via TraceLoggingWrite macros) will also have Id and Version set to 0.

Previously, TraceLoggingProvider.h would assign IDs to events at link time. These IDs were unique inside a DLL or EXE, but changed from build to construct and from module to module.

Leave a Reply

Your email address will not be published. Required fields are marked *