banner



Windows 10 SDK preview build 18980 now available for developers

Microsoft released another update to the Windows x SDK preview today. This release pushes the build number upward to 18980, which matches the latest Windows 10 build available for Windows Insiders in the Fast ring. The updated SDK is available to download from the Windows Insider website now.

Hither'due south a recap of all of the major changes in this release:

Tools updates

  • 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, information technology will exist read as a UTF-eight file. Otherwise, if information technology starts with a UTF-16LE BOM, information technology will be read every bit a UTF-16LE file. If the -u parameter was specified, it volition exist read as a UTF-16LE file. Otherwise, it will be read using the electric current code page (CP_ACP).
    • Now avoids one-definition-dominion (ODR) problems in MC-generated C/C++ ETW helpers caused past 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-eight or UTF-16 byte lodge mark (BOM) will be read as Unicode. Input files that exercise non 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.
    • At present supports Unicode output (.tmh) files. Past default, output files will exist encoded using the electric current code page (CP_ACP). Utilise command-line parameters -cp:UTF-eight or -cp:UTF-16 to generate Unicode output files.
    • Beliefs 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 bold a single-byte character set. This may atomic number 82 to beliefs changes in cases where the input files practice not conform to the current code page. In cases where this is a problem, consider converting the input files to UTF-eight (with BOM) and/or using the -cp:UTF-viii command-line parameter to avoid encoding ambivalence.
  • TraceLoggingProvider.h

    • Now avoids i-definition-dominion (ODR) issues caused by conflicting configuration macros (e.m. when ii .cpp files with alien 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++ lawmaking, the TraceLoggingWrite macro has been updated to enable amend code sharing between like events using variadic templates.
  • Signing your apps with Device Guard Signing

    • Nosotros are making it easier for you to sign your app. Device Guard signing is a Device Guard characteristic that is available in Microsoft Store for Business organisation 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 can exist found here: https://docs.microsoft.com/en-the states/windows/msix/package/signing-parcel-device-baby-sit-signing

Breaking changes

  • Removal of api-ms-win-cyberspace-isolation-l1-i-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-net-isolation-l1-i-0.lib can switch to OneCoreUAP.lib every bit 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 can switch to bthprops.lib as a drop-in replacement.

The updates and changes listed above come in addition to a diversity of API updates and removals, all of which yous tin can find in Microsoft'due south detailed release notes. As is typical for SDK preview releases, yous can install build 18980 alongside previous SDKs with Visual Studio 2022 and 2022.

We may earn a commission for purchases using our links. Acquire more.

Source: https://www.windowscentral.com/windows-10-sdk-preview-build-18980-now-available-developers

Posted by: gurleygracts1948.blogspot.com

0 Response to "Windows 10 SDK preview build 18980 now available for developers"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel