Windows 10 SDK preview build 17749 now available for developers

Microsoft has shipped out some other new Windows 10 SDK preview build for developers. Today's release brings the build number up to 17749.

If y'all've been following Microsoft's recent SDK releases, at that place are no surprises or new features here. The build largely focuses on problems fixes and changes to the API surface area. Still, every bit we go closer to the release of the Windows 10 October 2022 Update, Microsoft is probable putting the terminal touches of the SDK to be released alongside information technology.

Here's a recap of some of the highlights:

Support get_strong and get_weak to create delegates: This update allows a programmer to use either get_strong or get_weak instead of a raw this arrow when creating a delegate pointing to a member part.

Add async cancellation callback: The most ofttimes requested feature for C++/WinRT's coroutine support has been the addition of a cancellation callback.

Simplify the use of APIs expecting IBuffer parameters: Although nearly APIs prefer collections or arrays, enough APIs rely on IBuffer that it should be easier to utilise such APIs from C++. This update provides directly access to the information backside an IBuffer implementation using the aforementioned information naming convention used by the C++ standard library containers. This also avoids colliding with metadata names that conventionally begin with an uppercase letter.

Conformance: Improved support for Clang and Visual C++'due south stricter conformance modes.

Improved code gen: Various improvements to reduce code size, meliorate inlining, and optimize factory caching.

Remove unnecessary recursion: When the command line refers to a folder rather than a specific winmd, cppwinrt volition no longer search recursively for winmd files. It causes performance problems in the OS build and can pb to usage errors that are difficult to diagnose when developers inadvertently cause cppwinrt to consume more winmds than expected. The cppwinrt compiler as well now handles duplicates more intelligently, making it more resilient to user error and poorly-formed winmd files.

Declare both WINRT_CanUnloadNow and WINRT_GetActivationFactory in base.h: Callers don't need to declare them directly. Their signatures take too inverse, amounting to a breaking change. The declarations convalesce most of the pain of this change. The alter is necessitated by the fact that C++/WinRT no longer depends on the Windows headers and this change removes the dependency on the types from the Windows headers.

Harden smart pointers: The result revokers didn't revoke when move-assigned a new value. This atomic number 82 usa to take a closer look at the smart pointer classes and we noticed that they were non reliably handling self-assignment. This is rooted in the com_ptr class template that nearly of the others rely on. We fixed com_ptr and updated the outcome revokers to handle motion semantics correctly to ensure that they revoke upon assignment. The handle form template has as well been hardened by the removal of the implicit constructor that made it easy to write wrong code. This also turned bugs in the Os into compiler errors stock-still in this PR.

If you're a developer, you can catch Windows 10 SDK preview build 17733 from Microsoft's download page now.

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

History catches up

The problem for a consumer HoloLens was always the lack of Windows Phone

What is the futurity for Microsoft (and Windows) mixed reality? The latest report from Business Insider sheds some light, but this all comes back to ane major problem for Microsoft: No mobile Windows OS. But what about a futurity headset that is cloud-based? Some thoughts on what could happen for Microsoft mixed reality.