C++/WinRT

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
C++/WinRT
Original author(s)Kenny Kerr[1]
Developer(s)Kenny Kerr, Scott Jones, Ryan Shepherd
Initial releaseJune 23, 2015 (4 years ago) (2015-06-23)[2]
Stable release
2.0.190620.2 / 21 June 2019; 22 days ago (2019-06-21)[3]
Written inC++
Operating systemWindows
TypeSoftware development tools
LicenseMIT
Websitedocs.microsoft.com/windows/uwp/cpp-and-winrt-apis/

C++/WinRT is a C++ library for Microsoft's Windows Runtime platform, designed to provide access to modern Windows APIs. C++/WinRT is provided as a standard C++17 header file library, unlike C++/CX, which is an extension to C++ and requires a recent version of Microsoft Visual C++.[4]

C++/WinRT was introduced as part of the Microsoft Windows SDK in version 10.0.17134.0 (Windows 10, version 1803). Microsoft Visual Studio support for C++/WinRT is provided by an officially-supported extension.[5]

C++/WinRT was originally released in 2015 by Kenny Kerr, who shortly afterward joined Microsoft.[6] C++/WinRT is now Microsoft's recommended replacement for both the Windows Runtime C++ Template Library, and for C++/CX.[7]

Overview[edit]

Microsoft's Windows Runtime is based on Component Object Model (COM) APIs, and is designed to be accessed through language projections. A language projection hides the COM details, and provides a more natural programming experience for a given language. For C++ developers, C++/WinRT is the officially supported, modern C++ language projection.

As of version 10.0.17134.0 (Windows 10, version 1803), the Microsoft Windows SDK contains a header-file-based standard C++ library for consuming first-party Windows APIs (that is, Windows Runtime APIs in Windows namespaces).[7] C++/WinRT also ships with the cppwinrt.exe tool, which can be pointed at a Windows Runtime metadata (.winmd) file to generate a header-file-based standard C++ library that projects the APIs described in the metadata for consumption from C++/WinRT code. Windows Runtime metadata (.winmd) files provide a canonical way of describing a Windows Runtime API surface. By pointing the cppwinrt.exe tool at metadata, users can generate a library for use with any runtime class implemented in a second- or third-party Windows Runtime component, or implemented in their own application.

With C++/WinRT, users can also implement their own runtime classes using standard C++, without resorting to COM-style programming. For a runtime class, types can be described in a MIDL file (.idl), and from that file the midl.exe and cppwinrt.exe tools generate the implementation boilerplate source code files, ready for users to add their own implementation. Alternatively, users can just implement interfaces by deriving from a base class that's part of the C++/WinRT header library. These techniques employ the curiously recurring template pattern for function-calling via static dispatch. C++/WinRT makes use of a host of modern ISO C++11 (and later) language features to increase productivity and run-time performance. Features that were not available when C++/WinRT's predecessors (WRL and C++/CX) were designed.

Standard C++ data types, algorithms, and keywords are used with C++/WinRT; however, the projection also has its own custom data types.

C++/WinRT produces smaller binaries than other language options for the Windows Runtime.

History[edit]

Design and development of C++/WinRT was begun in 2014 by the then-independent software developer Kenny Kerr. At the time, the prevailing way for developers to call Windows Runtime APIs using C++ was with the C++/CX language projection. C++/CX adds non-standard extensions to the C++ language, such as the ref new and ^ (hat) notation inherited from C++/CLI. It hadn't been fully appreciated then that advances in ISO C++ language features meant that it had become possible to design a Windows Runtime language projection for standard C++, without extensions. "There are a lot of very experienced C++ developers at Microsoft who have spent decades-long careers working with C++ and COM," Kerr says. "I think it took someone who didn't realize that it was impossible to just try it anyway and show that it works."[6]

"I had had some previous experience projecting COM APIs into modern C++, so I decided to see whether I could apply those same techniques to the Windows Runtime." One early challenge in developing C++/WinRT was managing the trade-offs that the Windows Runtime makes to support projections for JavaScript and managed .NET languages out of the box. The complexity in the way that generic collections work across language projections is another example of these design challenges, as was coming up with an efficient way for standard C++ to handle the Windows Runtime's interface-versioning model. "It really pushed my understanding of C++ at that time, and it's since pushed the Microsoft Visual C++ compiler to more efficiently handle such techniques at this scale."

References[edit]

  1. ^ "Embracing Standard C++ for the Windows Runtime".
  2. ^ "Modern C++ for the Windows Runtime".
  3. ^ "C++/WinRT NuGet package".
  4. ^ stevewhims. "Introduction to C++/WinRT - Windows UWP applications". docs.microsoft.com. Retrieved 2019-07-10.
  5. ^ "C++/WinRT Visual Studio Extension".
  6. ^ a b How Kenny Kerr Brought C++/WinRT to Microsoft MSDN Magazine
  7. ^ a b Introduction to C++/WinRT docs.microsoft.com

External Links[edit]