UWPDumper VS Windows UI Library

I used shared memory pages a while ago when making UWPDumper since it helped bypass UWP's sandboxing. I only used it as a form of very fast IPC between a native windows process and a UWP process. I could potentially send entire files through a large window of shared memory if I wanted to. Shared pages even work on Windows-On-Arm surprisingly.

Have you only tried to mod the halo games on the windows store? While you are correct its not always been and might not always be true. There is a reason projects like this exist. I know you don't need that any more for mcc but its a good idea to not use the widows store for any game you plan on modding

I have a promising update for you. It appears like you can use UWPDumper to dump a UWP game to an unencrypted folder, and then run it with Lutris, though your luck may vary with this method.

UWP run in encrypted filesystem, maybe you can bypass it with UWPDumper but I really never used it, use at your own risk. https://github.com/Wunkolo/UWPDumper

2) download UWPDumper

Link: https://github.com/Wunkolo/UWPDumper

I wish that was true, but even the new stuff, like their new frameworks, performs poorly while their older frameworks perform really well. That's brand new code, with no legacy codebase to care for.

The reason why I don't recommend Winui is the million bugs it has. See the github issues page. All Microsoft ui stuff sucks currently. But if you use WPF why not FluentWPF

Development for WinAppSdk and WinUI 3 is also very slow and Microsoft seems to not want to push it and invest more developers into it for some reason. They try to improve the framework, is just it's a small team. For example it was a headacke to apply the Mica backgrop and required unmanaged code, they made it simpler and reduced it to a line of code but it took months. I have 2 out of 7 issues fixed on WinAppSdk repository and 0 out of 8 issues fixed in the WinUI 3 repository (some of the older than a year). This are just my issues, there are many other opened by other developers. So yeah, it wasn't fun at all. PoweshellSDK had an issue with the Import-Module command and it wasn't fixed for more than a year and probably won't be ever fixed, but I'm glad I found a workaround, even more clean and more safe, otherwise I couldn't have added the posibility to uninstall and change Store apps.

Compared to UWP or WPF, WinUI 3 is somewhere between 100-200% slower and consumes 7-20 times as much RAM as the old frameworks (for certain operations).