Windows 10 SDK preview build 19008 now available for developers
Microsoft has released another update to the Windows 10 SDK preview. The build number for this release comes in at 19008, which matches the build number of the latest Windows 10 Fast ring release. Developers tin can become their hands on the latest SDK preview from the Windows Insider website now.
The release notes in this build match those in previous releases for the 20H1 development wheel. Hither'south a recap of what'south new:
Tools updates
Message Compiler (mc.exe)
- Now detects the Unicode byte society 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. Otherwise, if information technology starts with a UTF-16LE BOM, information technology will exist read every bit a UTF-16LE file. If the -u parameter was specified, it will be read as a UTF-16LE file. Otherwise, it volition exist read using the current code page (CP_ACP).
- Now avoids ane-definition-dominion (ODR) problems in MC-generated C/C++ ETW helpers acquired by alien configuration macros (e.yard. when two .cpp files with conflicting definitions of MCGEN_EVENTWRITETRANSFER are linked into the same binary, the MC-generated ETW helpers volition now respect the definition of MCGEN_EVENTWRITETRANSFER in each .cpp file instead of arbitrarily picking ane or the other).
Windows Trace Preprocessor (tracewpp.exe)
- At present supports Unicode input (.ini, .tpl, and source code) files. Input files starting with a UTF-8 or UTF-sixteen byte order marking (BOM) will exist read as Unicode. Input files that do not start with a BOM volition be read using the current code folio (CP_ACP). For backwards-compatibility, if the -UnicodeIgnore control-line parameter is specified, files starting with a UTF-16 BOM volition exist treated as empty.
- Now supports Unicode output (.tmh) files. By default, output files volition be encoded using the current code page (CP_ACP). Use command-line parameters -cp:UTF-eight or -cp:UTF-xvi 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. Before versions of tracewpp avoided Unicode conversions and performed text processing assuming a unmarried-byte grapheme set. This may lead to beliefs changes in cases where the input files do not conform to the electric 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 ambivalence.
TraceLoggingProvider.h
- At present avoids one-definition-rule (ODR) issues acquired 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 ane or the other).
- In C++ code, the TraceLoggingWrite macro has been updated to enable better code sharing between similar events using variadic templates.
Signing your apps with Device Guard Signing
- We are making it easier for you to sign your app. Device Baby-sit signing is a Device Guard feature that is available in Microsoft Store for Business and Didactics. Signing allows enterprises to guarantee every app comes from a trusted source. Our goal is to make signing your MSIX parcel easier. Documentation on Device Guard Signing tin be found here: https://docs.microsoft.com/en-us/windows/msix/parcel/signing-packet-device-guard-signing
Breaking changes
- Removal of api-ms-win-net-isolation-l1-1-0.lib: In this release api-ms-win-net-isolation-l1-1-0.lib has been removed from the Windows SDK. Apps that were linking against api-ms-win-cyberspace-isolation-l1-1-0.lib can switch to OneCoreUAP.lib as a replacement.
- Removal of IRPROPS.LIB: In this release irprops.lib has been removed from the Windows SDK. Apps that were linking against irprops.lib tin can switch to bthprops.lib as a drop-in replacement.
Equally with other recent SDK releases, at that place are a number of API updates and changes in this build. You tin check out the total release notes from Microsoft for an in-depth look at the changes. Every bit usual, you can install this release adjacent to previous SDK build in Visual Studio.
We may earn a committee for purchases using our links. Learn more than.
UH OH
An net connection volition soon be required when setting up Windows 11 Pro
Microsoft has announced that later this year, users volition exist required to connect to the internet and sign-in with a Microsoft Account during the out of box setup experience on Windows xi Pro. Microsoft has already been enforcing this requirement on Windows eleven Dwelling since launch last October, and Windows 11 Pro is now expected to follow adapt soon.
Source: https://www.windowscentral.com/windows-10-sdk-preview-build-19008-now-available-developers
Posted by: andersoncrushe.blogspot.com
0 Response to "Windows 10 SDK preview build 19008 now available for developers"
Post a Comment