UWP Community Toolkit VS Windows UI Library

GitHub/WCT/Controls/DataGrid (source code for the control)

Started programming by writing some apps for Windows Phone later UWP during university. A few years ago I started collaborating a lot on GitHub to some Microsoft projects, like the Windows Community Toolkit. There I created a lot of new APIs and libraries, like all the new animation APIs and pipeline brush APIs, etc. I then also proposed adding some general .NET APIs to it, and that's how the MVVM Toolkit was born, along with other libraries which are now moved to the .NET Community Toolkit. Fast forward until about late 2020, and they pinged me saying the new Microsoft Store (which hadn't been announced yet back then) was using several of those new APIs I had written, so we started collaborating more so that I could add more functionality they needed. After that shipped, at some point there was a new opening to which I applied, and here I am in the Microsoft Store team and also leading the .NET Community Toolkit 🙂

https://github.com/CommunityToolkit/WindowsCommunityToolkit (now multiplateform)

For instance, recently Chaochao opened a PR for the Windows Community Toolkit to open source the whole custom animation helpers he developed for the Store, which are used to implement the morphing animations you see when scrolling in a product page. You can see a GIF and the whole code here and in the linked PR.

Specifically I am looking for AsyncRelayCommand.cs. All documentation points to CommunityToolkit repo but I can not find it there. Link to source repo from the Nuget package also points to CommunityToolkit. I am not looking for samples.

The report itself is just markdown that is rendered with the Community Toolkit's MarkdownTextBlock.

That's interesting. It will need some documentation and to finish the renaming at some point, e.g. Span2D is in https://github.com/CommunityToolkit/WindowsCommunityToolkit but as you say doesn't require Windows.

Windows Community Toolkit

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).