![\"Windows](\"https:\/\/devblogs.microsoft.com\/ifdef-windows\/wp-content\/uploads\/sites\/61\/2023\/08\/Header.light_.png\")
<\/a><\/p>\nIf you’re not familiar with the Windows Community Toolkit, see below here<\/a>! Or download our Sample Gallery<\/a> from the Microsoft Store to start exploring what it has available for WinUI developers.<\/p>\n The Toolkit’s dependencies have been updated to WindowsAppSDK<\/a> 1.6 and Uno Platform<\/a> 5.5 versions to take in fixes and updates we needed to support .NET 8 and address other issues within the Toolkit. As usual, the Toolkit should be be forward compatible with minor versions of these libraries and frameworks.<\/p>\n We’ve also updated our Win2D<\/a> dependency in this PR<\/a> which now means the base TFM required for building is again 19041 and should work with the default WinUI templates. We know this caused a lot of confusion for folks with the 8.1 release.<\/p>\n \u2757 Note<\/strong>: We’ve also updated to XAML Behaviors<\/a> 3.0 which unifies the namespaces for behaviors, you’ll need to apply that alignment when upgrading to change The Windows Community Toolkit supports Native AOT<\/a> for all platforms. Compiling your C# app with AOT can help improve performance and memory usage.<\/p>\n See the release notes<\/a> for some remaining known issues.<\/p>\n Link to the PR<\/a> from @Arlodotexe<\/a> \ud83d\udc51 Tracking issue is here<\/a>.<\/p>\n We have also added UWP Support for .NET 9<\/a>. See more details in the original preview blog here<\/a>. The Windows Community Toolkit still supports original receipe as well with .NET Native.<\/p>\n Link to the PR<\/a> from @Arlodotexe<\/a> \ud83d\udc51 And Sergio Pedri<\/a> \ud83d\udc51<\/p>\n Even though the XAML Llama originally created SwitchPresenter, and independently created the Link to PR<\/a> from the XAML Llama \ud83e\udd99<\/a> \ud83d\udc51<\/p>\n Thanks to PR<\/a> from Sergio Pedri<\/a> \ud83d\udc51<\/p>\n Also check out the additional Media\/Brush samples in the Windows Community Toolkit Gallery app<\/a> added by Erin Woo<\/a> in PR 639<\/a> \ud83c\udf89<\/p>\n While working on Windows Command Palette<\/a>, we noticed some issues with the current extensions for See more info in this PR<\/a> from XAML Llama \ud83e\udd99<\/a> \ud83d\udc51<\/p>\n For the entire list of bug fixes and changes in this update, see the full changelog on GitHub here<\/a>.<\/p>\n Big thanks to our community contributors! \ud83d\udc51<\/p>\n To help the process of starting new ideas and contributing to the Toolkit, we created Windows Community Toolkit Labs<\/a> as a place where we can incubate and iterate over new ideas, try things out without worry, see what gets used by the community, and then decide to bring them into the main repository when they’re ready and well-tested.<\/p>\n We’ve talked about Labs here before<\/a>, but the main goal is to help encapsulate our development processes from inception to polished product. It also helps us better understand what gets interest and excitement from our community before shipping something to our broader developer audience.<\/p>\n The best way to get involved with the Toolkit is to get involved with Windows Community Toolkit Labs. Setup the preview feed and pull down a package:<\/a>.<\/p>\n Then provide feedback on that experiment, that’s all it takes to get started contributing!<\/p>\n From there join in a discussion or start a new one<\/a> – we look forward to meeting you!<\/p>\n We have updated the Sample Gallery<\/a> in the Store to include the latest iterations of Labs components. Since our last release, we have two new experiments for you to try and provide feedback on:<\/p>\n Tired of using Let the compiler generate the rest of the mess for you! This takes advantage of the Thanks to PR<\/a> from Sergio Pedri<\/a> \ud83d\udc51<\/p>\n The Thanks to @h82258652<\/a> with this PR<\/a> to get this journey started! \ud83d\udc51<\/p>\n Not sure how to get started contributing? Don’t worry!<\/em> Did you know that just providing feedback on what we’re doing and trying our new components is contributing<\/strong>?!?<\/p>\n If you have a new idea for a control, API, or something, read more about Windows Community Toolkit Labs above<\/a>.<\/p>\n Join in our discussion about this 8.1 release on GitHub here<\/a>. We’re also active on Discord<\/em> in the Windows App Community<\/a> server You can also reach out on Social Media with the If you’re interested in contributing documentation or code, here are a few extra steps:<\/p>\n If you’re new here, the Windows Community Toolkit is a collection of controls for WinUI 2, WinUI 3, and Uno Platform developers that simplifies and demonstrates common developer tasks for building experiences on Windows 10 and Windows 11 with .NET.<\/p>\n Reminder that 8.x is a complete re-work<\/strong> of how the Windows Community Toolkit is built and published from top-to-bottom. Be sure to read the breaking changes and migration notes from our last release blog here<\/a> and on our wiki here<\/a>!<\/em>. In our 8.x update, we overhauled how we worked on the toolkit to enable targeting multiple platforms from a single-codebase<\/strong><\/em>, and to make it much easier to develop<\/strong>, maintain<\/strong>, and contribute<\/strong> Toolkit components.<\/p>\n The Toolkit is part of the .NET Foundation<\/a>. You can download our Sample Gallery<\/a> from the Microsoft Store to discover and try Toolkit components before getting started on your project. You can find an introduction video here<\/a>.<\/p>\n For those new to Uno Platform<\/a> \u2013 it enables building single-source C# and WinUI apps which run natively on Windows, iOS, Android, macOS, Linux and Web via WebAssembly. It offers Figma integration for design-development handoff, and a set of extensions to bootstrap your projects. Uno Platform is free and Open Source (Apache 2.0) and available on\u202fGitHub<\/a>.<\/p>\nAt a Glance \ud83d\udd0d<\/h2>\n
\n
\n
\n
\n
\n
<\/a> Important Changes<\/h2>\n
<\/a> Dependencies\/TFM<\/h3>\n
Microsoft.Xaml.Interactions.Core<\/code> to Microsoft.Xaml.Interactivity<\/code>.<\/p>\n<\/a> New Features \u2728<\/h2>\n
<\/a> Native AOT<\/h3>\n
<\/a> UWP Support for .NET 9<\/h3>\n
<\/a> SwitchConverter<\/h3>\n
SwitchPresenter<\/code> now accepts object<\/code> as content instead of being restricted to UIElement<\/code>, just like the base ContentPresenter<\/code> it is based on. This opens up many new possibilities, including using it with a DataTemplate<\/code> and swapping data for context, and the new<\/em> SwitchConverter<\/code>.<\/p>\n<\/a><\/p>\n<Page.Resources>\r\n <!-- SwitchConverter lets you easily convert general values to resources -->\r\n <converters:SwitchConverter x:Key=\"StatusToColorSwitchConverter\"\r\n TargetType=\"local:CheckStatus\">\r\n <!-- Note: These are reused from the controls namespace from SwitchPresenter -->\r\n <controls:Case Content=\"{ThemeResource SystemFillColorSuccessBrush}\"\r\n Value=\"Success\" \/>\r\n <controls:Case Content=\"{ThemeResource SystemFillColorCautionBrush}\"\r\n Value=\"Warning\" \/>\r\n <controls:Case Content=\"{ThemeResource SystemFillColorCriticalBrush}\"\r\n Value=\"Error\" \/>\r\n <\/converters:SwitchConverter>\r\n<\/Page.Resources>\r\n\r\n<StackPanel Spacing=\"8\">\r\n <ComboBox x:Name=\"StatusPicker\"\r\n Header=\"Pick a status\"\r\n SelectedIndex=\"0\">\r\n <x:String>Success<\/x:String>\r\n <x:String>Warning<\/x:String>\r\n <x:String>Error<\/x:String>\r\n <\/ComboBox>\r\n <TextBlock Text=\"This is it, this is the demo:\" \/>\r\n <TextBlock FontWeight=\"SemiBold\"\r\n Foreground=\"{x:Bind StatusPicker.SelectedItem, Converter={StaticResource StatusToColorSwitchConverter}, Mode=OneWay}\"\r\n Text=\"{x:Bind StatusPicker.SelectedItem, Mode=OneWay}\" \/>\r\n<\/StackPanel>\r\n<\/code><\/pre>\nSwitchConverter<\/code> after while tinkering on a project. We’ve discovered that a SwitchConverter<\/code> has existed in the past as well; so if you missed it from WPF, there’s one here now too! \ud83c\udf89<\/p>\n<\/a> Improvements<\/h2>\n
<\/a> AcrylicBrush in WinUI3<\/h3>\n
AcrylicBrush<\/code> is now re-enabled for WinUI 3. Note, as per WinUI 3 in general, the backdrop source is not enabled. You can use this now to composite within your application.<\/p>\n<\/a><\/p>\n<\/a> DispatcherQueueTimer.Debounce<\/h3>\n
DispatcherQueueTimer.Debounce<\/code>. This led us to a flurry of improvements and tests to ensure these extensions worked well and as expected in a variety of scenarios and mainted state better replacing the ConcurrentDictionary<\/code> with a ConditionalWeakTable<\/code>. This also led directly to future improvements in .NET itself<\/a> thanks to Sergio Pedri<\/a>!<\/p>\n<\/a> Bug Fixes \ud83d\udc1e<\/h3>\n
\n
<\/a> Windows Community Toolkit Labs \ud83e\uddea<\/h2>\n
https:\/\/pkgs.dev.azure.com\/dotnet\/CommunityToolkit\/_packaging\/CommunityToolkit-Labs\/nuget\/v3\/index.json\r\n<\/code><\/pre>\n<\/a> DependencyPropertyGenerator<\/h3>\n
propdp<\/code> everywhere and all the boiler-plate required for Dependency Properties? Well try out the new source generator which makes them super simple to use!<\/p>\npublic partial class MyControl : DependencyObject\r\n{\r\n [GeneratedDependencyProperty(DefaultValue = 42)]\r\n public partial int Number { get; set; }\r\n}\r\n<\/code><\/pre>\npartial<\/code> properties added in C# 13.<\/p>\n<\/a> OpacityMaskView<\/h3>\n
<\/a><\/p>\nOpacityMaskView<\/code> allows complex brush compositing with transparency to let content behind an element appear through. It is a ContentControl<\/code> that wraps another element.<\/p>\n<\/a> Feedback & Contributing<\/h2>\n
#community-toolkit<\/code> channel here<\/a>.<\/p>\n#WindowsCommunityToolkit<\/code> hashtag. Find us at @XAMLLlama<\/a>, @xamlllama.bsky.social<\/a>, @XAMLLlama@hachyderm.io<\/a>, @Niels9001<\/a>,\nand @Arlodottxt@fosstodon.org<\/a>.<\/p>\n\n
OpenSolution.bat<\/code> file for a component and try to build it following the steps in the readme.<\/li>\n<\/a> About the Windows Community Toolkit<\/h2>\n
About Uno Platform<\/h2>\n
<\/a><\/p>\n