It is embarrassing (for Microsoft) how much better Rider is for C# than Visual Studio.
C++/CX was deprecated and replaced by C++/WinRT in 2016.
To this day, to develop WinUI C++ applications, there is no built-in tooling in VS, you need to manually generate and merge C++ code out of IDL files, which have zero support on Visual Studio for syntax highlighting and code completion, unless you reach out to some third party plugins.
To top that, given the way things turned out, C++/WinRT is now in maintenance, no goals to ever move it past C++17, or improve Visual Studio developer experience.
I doubt that they feel embarassed by this outcome.
Multiple inheritance in C++ is a can of worms, unless you're prepared to deal with the related issues of virtual base classes, and diamond inheritance.
That is why after C++ all the languages that support multiple inheritance do so only at the interface level and not implementation code, or rather go with a mix-ins approach.
And in regards to Microsoft world, well the same developers that weren't happy with VCL and Pascal, and in for a treat given that the only modern way to do native Windows UIs in Microsoft world is via .NET consuming DLLs/COM/WinRT, unless they want to either stick with MFC, or the outdated tooling in C++/WinRT.
With regards to multiple inheritance, this was the C++ Builder criticism, not mine. That and the extra macros needed to support the VCL. I was a Delphi guy, so I appreciated that the Object Pascal version of using the VCL was cleaner to use than the C++ interface.
We no longer use C++ for UI. Any native code is wrapped up in to P/Invokes. I think all of our MFC apps are EOL now. Everything is WPF or Maui for cross platform.