It strikes me that having the C++ requirement is part of what makes this difficult. I'd like to have seen some reasoning why not to just use C#. Seems like it could have made some things easier, especially given the author's praise of XAML and acceptance of Visual Studio.
I'm not saying C# is better than C++, but just that choosing one over the other does have an impact.
> It strikes me that having the C++ requirement is part of what makes this difficult.
It doesn't.
In fact, it makes the problem even easier to solve due to the options that are already on the table. Virtually all .NET-based frameworks support C++ besides C#, specially WinUI3.
I'm not saying C# is better than C++, but just that choosing one over the other does have an impact.