The first Windows 10 SDK Preview build for 20H1 is now available - here's what's new

Microsoft is already preparing the 20H1 update for Windows 10, which is set to be released early next year, and a few builds of the OS have been released for Insiders so far. Today, Microsoft also released the first preview build of the Windows 10 SDK in preparation for the 20H1 update, and it's build 18890.

This is the first build to be released after the SDK for the Windows 10 May 2019 Update was finalized, and as such, it's also the first one in a while to actually have some new changes. Among the news are updates to the Message Compiler, Windows Trace Preprocessor, and more:

Message Compiler (mc.exe)

Now detects the Unicode byte order mark (BOM) in .mc files. If the If the .mc file starts with a UTF-8 BOM, it will be read as a UTF-8 file. If it starts with a UTF-16LE BOM, it will be read as a UTF-16LE file. Otherwise, if the -u parameter was specified, it will be read as a UTF-16LE file. Otherwise, it will be read using the current code page (CP_ACP).

Now avoids one-definition-rule (ODR) problems in MC-generated C/C++ ETW helpers caused by conflicting configuration macros (e.g. when two .cpp files with conflicting definitions of MCGEN_EVENTWRITETRANSFER are linked into the same binary, the MC-generated ETW helpers will now respect the definition of MCGEN_EVENTWRITETRANSFER in each .cpp file instead of arbitrarily picking one or the other).

Windows Trace Preprocessor (tracewpp.exe)

Now supports Unicode input (.ini, .tpl, and source code) files. Input files starting with a UTF-8 or UTF-16 byte order mark (BOM) will be read as Unicode. Input files that do not start with a BOM will be read using the current code page (CP_ACP). For backwards-compatibility, if the -UnicodeIgnore command-line parameter is specified, files starting with a UTF-16 BOM will be treated as empty.

Now supports Unicode output (.tmh) files. By default, output files will be encoded using the current code page (CP_ACP). Use command-line parameters -cp:UTF-8 or -cp:UTF-16 to generate Unicode output files.

Behavior change: tracewpp now converts all input text to Unicode, performs processing in Unicode, and converts output text to the specified output encoding. Earlier versions of tracewpp avoided Unicode conversions and performed text processing assuming a single-byte character set. This may lead to behavior changes in cases where the input files do not conform to the current code page. In cases where this is a problem, consider converting the input files to UTF-8 (with BOM) and/or using the -cp:UTF-8 command-line parameter to avoid encoding ambiguity.

TraceLoggingProvider.h

Now avoids one-definition-rule (ODR) problems caused by conflicting configuration macros (e.g. when two .cpp files with conflicting definitions of TLG_EVENT_WRITE_TRANSFER are linked into the same binary, the TraceLoggingProvider.h helpers will now respect the definition of TLG_EVENT_WRITE_TRANSFER in each .cpp file instead of arbitrarily picking one or the other).

In C++ code, the TraceLoggingWrite macro has been updated to enable better code sharing between similar events using variadic templates.

There's also one breaking change, which is the removal of irprops.lib, so developers linking to it will now have to link to bthprops.lib instead. Additionally, the build brings a number of new APIs since Windows 10 version 1903.

As usual, it's worth noting that the latest SDK preview can be used side-by-side with previous SDKs and with Visual Studio 2017 or higher. You can continue to submit apps that target Windows 10 version 1903 to the Store. Additionally, this build will only work with Windows Insider Preview builds.

You can download the latest SDK preview build here. The accompanying versions of the Hardware Lab Kit (HLK), Assessment and Deployment Kit (ADK), and Windows Driver Kit (WDK) are also available.

Report a problem with article
1555616365_edgedev
Next Article

Edge Dev build 76.0.152.0 is now available with spellcheck and a ton of changes

1557434994_microsoft_to-do_banner
Previous Article

Microsoft To-Do and Planner integration now available for users on all platforms

0 Comments - Add comment

Advertisement