Stats
windows-toolkit/WindowsCommunityToolkit is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
UWP Community Toolkit Alternatives
Similar projects and alternatives to UWP Community Toolkit based on common topics and language
-
ReactiveUI
An advanced, composable, functional reactive model-view-viewmodel framework for all .NET platforms that is inspired by functional reactive programming. ReactiveUI allows you to abstract mutable state away from your user interfaces, express the idea around a feature in one readable place and improve the testability of your application. (by reactiveui)
-
-
Scout APM
Scout APM - Leading-edge performance monitoring starting at $39/month. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.
-
Uno Platform
Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
-
Windows UI Library
Windows UI Library: the latest Windows 10 native controls and Fluent styles for your applications
-
RGBMaster
A .NET app that runs in the background and synchronises the matching colour of the background sound to both Razer Chroma's devices & Xiaomi Yeelight bulbs.
-
-
Feed-Manager-WPF-App
RSS Feed Downloader and local file manager in a modern WPF Metro Design and MVVM Design Pattern.
Posts
-
Announcing the Microsoft.Toolkit HighPerformance 7.0 release
Here's a blog post I wrote about all the new features I've added to this new major release of the Microsoft.Toolkit.HighPerformance package. It's part of the Windows Community Toolkit, which is a collection of libraries with helpers, extensions and controls for both cross-platform .NET developers, as well as UWP/WinUI 3 developers. If you want to learn more about the other features that were included in this new major release of the WCT, you can check out the official announcement blog post here and visit our repository here.
Yeah I made a PR for that here, but it was fundamentally an incredibly unsafe hack that we ultimately deemed not worth it to include, especially as it could've caused some friction with the .NET team in case any customers had opened an issue on their repo after misusing the Ref type or just stumbling into some weird GC/runtime bug around that. The current implementation is just marginally slower but still works, and also there's plans to bring native ref T fields to C# in the future (not yet certain whether it'll make it into C# 10 though), so we figured there was no point in taking that risk for what would've ultimately just be a temporary optimization just for a very, very niche API, just for a subset of users only using .NET Core or .NET 5 😄