When I was involved with Win32 Office, this (or the moral equivalent with VS Code) was often the case. Proper Visual Studio support was kludgy and difficult to maintain, and many (myself included) did without.
Most of the major desktop product groups have 30+ year old codebases and sure as hell aren't working off the latest C++, let alone C++/WinRT bindings. They've got other tools, or just put up with the drudgery because it's all they know.
How else can someone praise C++/WinRT versus the capabilities of C++/CX, which was finally something on the Microsoft side that could be compared with C++ Builder.
Sure it is an uplevel from WRL, however almost no one outside Redmod ever cared that WRL existed.
The only way to consider C++/WinRT on its present state as good is if the person in question never knew anything better, including MS own tooling.
He missed two important point that really puts me off.
The continuous reboots since Windows 8 was introduced.
The complete lack of respect for paying customers to deprecate C++/CX in name of ISO C++17 compatibility, with C++/WinRT, without any kind of Visual Studio tooling support, even after 4 years in development.
So now any .NET Native developer that would be dealing with C++/CX for those APIs that the WinDev refuses to create WinRT bindings, needs to write IDL files without any tooling, copy and merge generated files into their projects.
Wait for ISO C++ to get reflection and maybe we will do something about it they say.
Sometimes I get the feeling WinDev requires Notepad as their IDE.
Speaking of .NET Native, it is in maintenance, expect nothing beyond .NET Core 3.1 / C# 7.3.