driver1998

Also this will unblock the XAML islands on .NET 5+ scenario, without this we'll have to wait for WinUI 3 XAML islands which is "scheduled to a later release".

.NET 5 / 6 / 7 won't be compatible with AppContainer and UAP-only environments anytime soon, so UWP is not actually relevant here. This is mainly for XAML islands.

That sounds like great news, I am always baffled by the lack of XAML islands support in .NET 5/6.

For those are interested, @gus33000's fork of CsWinRT is at https://github.com/gus33000/CsWinRT/tree/wux.

> Mainly you have interop classes for .NET/WinRT that can currently only be applied to Windows.UI.Xaml or Microsoft.UI.Xaml I guess it should be fine to split CsWinRT into two libraries...

handling of IMEs seems broken: 

`DWMWA_USE_IMMERSIVE_DARK_MODE` is listed in https://docs.microsoft.com/en-us/windows/win32/api/dwmapi/ne-dwmapi-dwmwindowattribute now, but with no further descriptions. Is it going to be documented?

WinForms is a .NET warpper on top of user32 and comctl32, it also has these issues. On the other side, comctl32 controls are by definition based on GDI, and have...

> since there is no usable aarch64 mingw toolchain Maybe take a look at https://github.com/mstorsjo/llvm-mingw? Haven't tried DXVK with it but a lot of sizable projects (ffmpeg, qt, vlc, etc)...

C++/WinRT Upstream is working on improving MinGW support, and should already work with GCC 12 and LLVM 15. I don't think YoloRT would be necessary anymore. see: https://github.com/mstorsjo/llvm-mingw/issues/307 https://github.com/alvinhochun/mingw-w64-cppwinrt Also...