Today, we discharged another Windows 10 Preview Build of the SDK to be utilized related to Windows 10 Insider Preview (Build 18956 or more prominent). The Preview SDK Build 18956 contains bug fixes and being worked on changes to the API surface zone.
The Preview SDK can be downloaded from designer area on Windows Insider.
For input and updates to the windows 10 update known issues, if it’s not too much trouble see the engineer discussion. For new engineer 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 additionally keep on presenting your applications that target Windows 10 manufacture 1903 or prior to the Microsoft Store.
The Windows SDK will now officially just be bolstered by Visual Studio 2017 and more prominent. You can download the Visual Studio 2019 here.
This work of the Windows SDK will introduce on just on Windows 10 Insider Preview fabricates.
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_18956_1.iso.
Message Compiler (mc.exe)
Presently recognizes the Unicode byte request mark (BOM) in .mc records. On the off chance that the If the .mc record begins with an UTF-8 BOM, it will be perused as an UTF-8 document. 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 indicated, it will be perused as an UTF-16LE document. Else, it will be perused utilizing the present code page (CP_ACP).
Presently keeps away from one-definition-rule (ODR) issues in MC-produced C/C++ ETW assistants brought about by clashing design macros (for example whenever two .cpp documents with clashing meanings of MCGEN_EVENTWRITETRANSFER are connected into a similar paired, the MC-produced ETW aides will currently regard the meaning of MCGEN_EVENTWRITETRANSFER in each .cpp record rather than self-assertively picking either).
Windows Trace Preprocessor (tracewpp.exe)
Presently bolsters Unicode input (.ini, .tpl, and source code) records. Information records beginning with an UTF-8 or UTF-16 byte request mark (BOM) will be perused as Unicode. Info records that don’t begin with a BOM will be perused utilizing the present code page (CP_ACP). For in reverse similarity, if the – UnicodeIgnore order line parameter is indicated, documents beginning with an UTF-16 BOM will be treated as unfilled.
Presently bolsters Unicode yield (.tmh) documents. Of course, yield records will be encoded utilizing the present code page (CP_ACP). Use order line parameters – cp:UTF-8 or – cp:UTF-16 to create Unicode yield documents.
Conduct change: tracewpp now changes over all information content to Unicode, performs preparing in Unicode, and changes over yield content to the predefined yield encoding. Prior variants of tracewpp stayed away from Unicode changes and performed content preparing expecting a solitary byte character set. This may prompt conduct changes in situations where the info documents don’t adjust to the present code page. In situations where this is an issue, consider changing over the information documents to UTF-8 (with BOM) and additionally utilizing the – cp:UTF-8 direction line parameter to abstain from encoding vagueness.
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 parallel, the TraceLoggingProvider.h aides will presently regard the meaning of TLG_EVENT_WRITE_TRANSFER in each .cpp document rather than discretionarily picking either).
In C++ code, the TraceLoggingWrite full scale has been refreshed to empower better code sharing between comparable occasions utilizing variadic layouts.
Marking your applications with Device Guard Signing
We are making it simpler for you to sign your application. Gadget Guard marking is a Device Guard highlight that is accessible in Microsoft Store for Business and Education. Marking enables ventures to ensure each application originates from a confided in source. We will probably make marking your MSIX bundle simpler. Documentation on Device Guard Signing can be found here: https://docs.microsoft.com/en-us/windows/msix/bundle/marking bundle gadget protect marking
Expulsion of IRPROPS.LIB
In this discharge irprops.lib has been expelled from the Windows SDK. Applications that were connecting against irprops.lib can change to bthprops.lib as a drop-in substitution.