ProjectReunion VS cppwinrt

The issue is described here: WebView2 does not support passing in a CoreWebView2Environment · Issue #1170 · microsoft/WindowsAppSDK (github.com)

.. and how many of the Microsoft applications actually use WinUI3? As far as I can tell they're doing their own thing (Office) or are Electron (Teams) or, at least in Windows 10, haven't actually been updated from WinForms.

The overhead of WinUI3 is pretty huge. The visual designer, a winning feature of Visual Studio for decades, is AWOL. Why? It's XAML, the same as the previous XAML designer! It's just .. broken?

The backward compatibility story is a disaster: you can get stuck in the UWP sandbox https://github.com/microsoft/WindowsAppSDK/issues/1780

What's the big Microsoft WinUI3 flagship app, then? Something people are actually using? Rather than just a few system dialogues. (How many Win11 settings pop up a Win32 dialogue box, still?)

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.

As far as I know, there are still some issues with OIDC integration. See this, for example.

this I'm interested in. WinAppSDK is open source.

I think the issue is actually the sandboxing and other stuff. WinRT StorageProvider API is known to be extremely slow and NTFS / Windows IO subsystem is itself already quite slow compared to UNIX. The issue IIRC is that StorageProvider is designed for sandboxing and the way they implemented that involves doing RPCs to other processes. So there's probably some heavy context switching involved, but it's architectural, and so the voice recorder was never fixed.

https://github.com/microsoft/WindowsAppSDK/issues/8

Disclaimer: I work for Microsoft. I even work on WindowsAppSDK just not the WinUI parts. People far more graphically inclined and talented than I handle that 😀

Windows Runtime (WinRT) seems to be something they are working on. From what I could read are there a bunch of stuff needed apart from just a development library. I guess you meant this: https://github.com/microsoft/cppwinrt

Yeah, I closed it because it didn't seem to be taken into consideration, as later proven by https://github.com/microsoft/cppwinrt/issues/1123

std::future could be 'awaitable' (by implementing a struct coroutine_traits> + operator co_await) in a free function BUT VS2019 removed support for the nonstandard free function pattern for awaitable objects in PR702. Therefore we cannot add a co_await operator without modifying std::future source code.

You mean the cppwinrt library right? I thought you were referring to a book - and I couldn't find it on Amazon. LOL.