Today, we discharged another Windows 10 Preview Build of the SDK to be utilized related to Windows 10 Insider Preview (Build 18970 or more prominent). The Preview SDK Build 18970 contains bug fixes and a work in progress changes to the API surface territory.
The Preview SDK can be downloaded from designer segment on Windows Insider.
For input and updates to the known issues, it would be ideal if you see the designer gathering. For new designer highlight demands, head over to our Windows Platform UserVoice.
Things to note:
.This construct works related to recently discharged SDKs and Visual Studio 2017 and 2019. You can introduce this SDK and still likewise keep on presenting your applications that target Windows 10 form 1903 or prior to the Microsoft Store.
.The Windows SDK will now officially just be office install upheld by Visual Studio 2017 and more noteworthy. You can download the Visual Studio 2019 here.
.This work of the Windows SDK will introduce on just on Windows 10 Insider Preview manufactures.
.So as to help with content access to the SDK, the ISO will likewise have the option to be gotten to through the accompanying static URL: https://programming download.microsoft.com/download/sg/Windows_InsiderPreview_SDK_en-us_18970_1.iso
Message Compiler (mc.exe)
.Presently identifies the Unicode byte request mark (BOM) in .mc documents. In the event that the If the .mc document begins with an UTF-8 BOM, it will be perused as an UTF-8 record. office 365 setup with key Something else, on the off chance that it begins with an UTF-16LE BOM, it will be perused as an UTF-16LE document. In the event that the – u parameter was determined, it will be perused as an UTF-16LE record. Else, it will be perused utilizing the present code page (CP_ACP).
.Presently stays away from one-definition-rule (ODR) issues in MC-created C/C++ ETW partners brought about by clashing setup macros (for example whenever two .cpp records with clashing meanings of MCGEN_EVENTWRITETRANSFER are connected into a similar parallel, the MC-produced ETW assistants will presently regard the meaning of MCGEN_EVENTWRITETRANSFER in each .cpp document rather than discretionarily picking either).
Windows Trace Preprocessor (tracewpp.exe)
Presently underpins Unicode input (.ini, .tpl, and source code) documents. Info records beginning with an UTF-8 or UTF-16 byte request mark (BOM) will be perused as Unicode. Info documents that don’t begin with a BOM will be perused utilizing the present code page (CP_ACP). For in reverse similarity, if the – UnicodeIgnore direction line parameter is indicated, documents beginning with an UTF-16 BOM will be treated as unfilled.
Presently underpins Unicode yield (.tmh) documents. Naturally, yield records will be encoded utilizing the present code page (CP_ACP). Use direction line parameters – cp:UTF-8 or – cp:UTF-16 to produce Unicode yield records.
Conduct change: tracewpp now changes over all info content to Unicode, performs handling in Unicode, and changes over yield content to the predefined yield encoding. Prior forms of tracewpp kept away from Unicode transformations and performed content preparing expecting a solitary byte character set. This may prompt conduct changes in situations where the info records don’t fit in with the present code page. In situations where this is an issue, consider changing over the info records to UTF-8 (with BOM) as well as utilizing the – cp:UTF-8 direction line parameter to abstain from encoding equivocalness.
Presently maintains a strategic distance from one-definition-rule (ODR) issues brought about by clashing setup macros (for example whenever two .cpp records with clashing meanings of TLG_EVENT_WRITE_TRANSFER are connected into a similar twofold, the TraceLoggingProvider.h aides will currently regard the meaning of TLG_EVENT_WRITE_TRANSFER in each .cpp document rather than subjectively picking either).
In C++ code, the TraceLoggingWrite full scale has been refreshed to empower better code sharing between comparable occasions utilizing variadic layouts.