cppwinrt

Easy, that is the beauty of recordings, You can start by when C++/CX was replaced, CppCon 2016: “Embracing Standard C++ for the Windows Runtime" https://www.youtube.com/watch?v=lm4IwfiJ3EU With the followup talk the year thereafter, CppCon 2017: “C++/WinRT and the Future of C++ on Windows” https://www.youtube.com/watch?v=7TdpWB_vRZM Except the Visual Studio tooling comparable to C++/CX never came to be, using C++/WinRT feels to this day like using ATL with Visual C++ 6.0, except "This isn't meant as a negative statement. cppwinrt has reached all of its goals and is generally considered complete and largely bug-free (1). Whether WinRT/WinUI/WinAppSDK is the future is debatable. My experience has shown me that the Windows operating system is at its best when you embrace the Windows API as a whole, including Win32/COM/WinRT, and not just the

Anything related to WinUI is a bad joke. Have fun following the discussions and amount of bugs, https://github.com/microsoft/microsoft-ui-xaml That C++ support that WinUI team marketing keeps talking about relies on a framework that is no longer being developed. > The reason the issues page only lets you create a bug report is because cppwinrt is in maintenance mode and no longer receiving new feature work. cppwinrt serves an important and specific role, but further feature development risks destabilizing the project. Additional helpers are regularly contributed to complimentary projects such as https://github.com/microsoft/wil/. From https://github.com/microsoft/cppwinrt/issues/1289#issuecomme...

100% great advice, but really better go with Avalonia, Uno, WPF, Windows Forms, WinUI 3.0 only if one is a Microsoft employee. https://github.com/microsoft/microsoft-ui-xaml/issues https://github.com/microsoft/WindowsAppSDK/issues https://github.com/microsoft/CsWinRT/issues https://github.com/microsoft/cppwinrt/commits/master/

Cppwinrt is in maintenance mode[1]. Cppwin32 is abandoned (with windows.h as the official alternative). It is now possible to deploy WinUI 3 apps as single files in C#[2] but not in C++. From experience, the entire C++ side of WinUI 3 documentation is underbaked to the extent that the easiest approach is to read the C# documentation and attempt to guess the cppwinrt equivalent (as docs for cppwinrt are not really... there). I don’t know if they’ve really abandoned C++ entirely—the compiler team certainly hasn’t, that’s true. But the above doesn’t feel like first-class support. [1] https://github.com/microsoft/cppwinrt/issues/1289#issuecomme... [2] https://learn.microsoft.com/en-us/dotnet/core/deploying/sing...

Supposedly is being worked on for making it more Native AOT friendly. How we got into this mess? WinDev and DevDiv politcs. After the Longhorn debacle, its technologies landed on DevDiv, like WCF and WPF. Sinofsky and friends never were that keen in having .NET coming into their turf, it is no surprise that Hilo sample for Windows 7, then praises COM and C++ for Windows applications[0][1]. Then coming in this path, WinRT came to be, with roots as how .NET was being designed, before Microsoft decided to pivot it as another Java like technology[2]. A bunch of folks in WinDev, weren't happy with C++/CX, so they united to replace it with C++/WinRT, because extensions, when clang and GCC are full of extensions, promised to give back a C++/CX like developer experience in 2017[3], never delivered, went to have fun with Rust/WinRT. Now C++/WinRT

They wrote a Swift language projection for WinRT, akin to Microsoft's projections for standard C++ and Rust. https://github.com/thebrowsercompany/swift-winrt https://github.com/microsoft/cppwinrt https://github.com/microsoft/windows-rs

Ignore all the talk about WinUI 3.0 being the future, and check the issues on the following repos: https://github.com/microsoft/microsoft-ui-xaml https://github.com/microsoft/WindowsAppSDK https://github.com/microsoft/cppwinrt https://github.com/microsoft/CsWinRT

It's coming: https://github.com/microsoft/cppwinrt/pull/556/commits/6b957...

> Vtables and cross-language inheritance is interesting but difficult. Windows' COM "solved" that problem. For example see C++/WinRT[0] for a modern C++ interface to COM. Or the C# .NET equivalents. [0] https://github.com/Microsoft/cppwinrt

> I'm something of an outlier here, maintaining a big legacy MFC application that targets Windows CE, but I can't be the only one. The problem is not developing "legacy" apps, it's comparing the development and maintenance of "legacy" apps with apps that just get started being written today, for which the bare minimum is being cross-platform. > Are there wrappers for things like dlopen()? posix_madvise? Actually, yes, in a cross-platform way: * http://www.boost.org/doc/libs/1_65_1/doc/html/boost_dll.html (does dlopen, dlclose, and so much more) * http://www.boost.org/doc/libs/1_65_1/doc/html/boost/interpro... (advise() == posix_madvise if available) > Filesystem ACLs ? none that I know of :( though MS has a fairly decent "modern C++" API that covers WinRT: https://github.com/Microsoft/cppwinrt but I don't think ACLs are even available in

Don't know, but it's been discussed publicly rather recently: https://github.com/Microsoft/cppwinrt https://msdn.microsoft.com/en-us/magazine/mt745094.aspx "Teams within Microsoft are already starting to use C++/WinRT to build WinRT components for the OS itself."

I'm not a C++ developer by trade (mostly C#) but this looked compelling when I was looking to create high performance Windows app middleware: https://github.com/microsoft/cppwinrt

Similar tricks[0] can be used on Win32 applications. Although, I never got Intellisense working in VS if I declare #using <windows.winmd> in C++/Win32 projects. A simpler and a lot more interesting alternative (for Win32) is the excellent cppwinrt library[1] [0] https://software.intel.com/en-us/articles/using-winrt-apis-f... [1] https://github.com/Microsoft/cppwinrt

There is a new XAML feature called x:Bind where the XAML compiler code-gens the data binding code instead of the framework doing it all at runtime. You can set breakpoints in the generated code. https://msdn.microsoft.com/en-us/windows/uwp/xaml-platform/x... Instead of C++/Cx, you can use the new C++/WinRT, which uses standard C++ syntax and adds "await" to make async programming much easier. https://github.com/Microsoft/cppwinrt