Was and still is, I don't really grasp what kind of Stockholm syndrome goes by at WinDev, that they finally had something that could match against C++ Builder (UWP with C++/CX), only to kill it via a mini-riot, replacing it with a development experience akin to doing ATL with Visual C++ 6.0.
If only IDL tooling, and related C++ code generation wasn't frozen in time, just like it first came in Visual Studio almost 30 years ago, besides updating the actual language to MIDL 3.0, that is.
And now while WinUI 3.0 folks tell the story that you can use C++ with WinUI / WinAppSDK, what they don't tell is the castastrophic state of C++/WinRT tooling in Visual Studio, that there are no plans to improve it past C++17, and the only thing happening ot its repo is bug fixes.
Stay away from it as much as possible, and using it with C# and CsWinRT is not much better, as many errors are surfaced as HRESULT exceptions, and you need to actually single step into C++/WinRT code to actually find out the real cause.
