“These Aren't the COM Objects You're Looking For”
summary
Windows COM is 25 years old but using C++17 plus the C++/WinRT projection radically shrinks boilerplate and beats handwritten ABI code in size and speed; examples include RAII wrappers for CoInitializeEx, legacy helpers like _bstr_t and CComBSTR, and migration of an Advanced Installer codebase that mixes ATL/WTL GUI with WinRT APIs. The Windows Runtime uses winrt::hstring (not BSTR) and string_view is presented as the glue for UTF‑16 interop; practical gotchas and allocation/ownership rules are shown.
AI-written summary · about
chapters (12)
- 0:00Start
- 8:56Error-Checking
- 10:27Threaded Model
- 13:39Strings
- 14:24What's the Calm String Type
- 31:22Tlc String
- 36:28Windows Runtime
- 37:09How Do I Get Access to the Windows Runtime from C + +
- 37:26Windows Runtime C + + Template Library
- 41:24The Windows Runtime String Type
- 46:54The Windows Runtime
- 48:09What's the Cpp Winrt String Type
related talks
58m“Embracing Standard C++ for the Windows Runtime"
01h 05mC++/WinRT and the Future of C++ on Windows
51mNavigating Win32 App Development with WinUI and WPF
01h 04mMaking C++ and the STL Work in the Linux / Windows Kernels
01h 37mC++ And Beyond: Discussion
54mWriting C++ to Be Read
01h 16mPolymorphism, Cohesion, and Coupling in C++
01h 07mDesign Patterns in Modern C++