Skip to content

Releases: CommunityToolkit/Windows

[Pre-release] v8.2.241112-preview1

14 Nov 04:53
Compare
Choose a tag to compare
Pre-release

What's Changed

You don't need to modify your TFM off of 19041 anymore! This was a problem for folks with 8.1, but has now been fixed by working with the dependency that caused this original bump, thanks everyone for the feedback! Enjoy!

New Controls

Native AOT Support

For a remaining list of known issues with AOT, see this issue. Most are with specific samples vs. components, we're currently aware of issues with WrapLayout.

Bug Fixes

  • Updated Microsoft.Graphics.Win2D package reference to version 1.3.0, downgrade TFM back to 19041 by @Arlodotexe in #540
  • Enabled 'AcrylicBrush' in WinUI 3 again by @Sergio0694 in #488
  • Update _toolTip even if toolTipText isn't available by @dotMorten in #479
  • chore: update typos in class properties summary by @ajpinedam in #471

Infrastructure

New Contributors

Full Changelog: v8.1.240916...v8.2.241112-preview1

v8.1.240916

16 Sep 22:37
28e6925
Compare
Choose a tag to compare

See main 8.1 release notes here

Minor hotfix

What's Changed

Full Changelog: v8.1.240821...v8.1.240916

Join discussion here

v8.1.240821

22 Aug 16:14
Compare
Choose a tag to compare

See more information on our release blog here

What's Changed

Important Changes

Dependencies/TFM

The Toolkit’s dependencies have been updated to the latest WindowsAppSDK 1.5 and Uno Platform 5.2 versions to take in fixes and updates we needed to support .NET 8 and address other issues within the Toolkit.

When consuming the Toolkit, you must target Windows version 22621 instead of the prior 18362, i.e. if you were targeting net6.0-windows10.0.18362, you would target net6.0-windows10.0.22621 instead now.

Be sure to update the TargetFramework in your csproj AND your publishing profile xml (if you have it there too).

This does not affect your ability to run down-level with the minimum target version, that remains at 17763.

Older Package NuGet Redirects

Many older 7.x and below NuGet packages of the Windows Community Toolkit have been updated to redirect to their closest matching 8.1 counterparts.

For instance:

  • Microsoft.Toolkit.Uwp.UI.Controls.Primitives now redirects to CommunityToolkit.Uwp.Controls.Primitives
  • CommunityToolkit.WinUI.UI.Controls.Primitives now redirects to CommunityToolkit.WinUI.Controls.Primitives
  • and so on for other packages.

The redirects help raise awareness about the new package names for developers who want to use the latest from the Windows Community Toolkit. You should see these notifications within Visual Studio on older projects. If you're updating from 7.x packages, see our migration guide here.

Highlights

Samples

Bug Fixes

  • [SettingsExpander] Fix CornerRadius bug by @niels9001 in #329
  • Fix: AdvancedCollection inserts at wrong position when adding to end of source collection by @Poker-sang in #309
  • Segmented - Update EqualPanel to avoid Layout Cycle by @qhy040404 in #360
  • [GridSplitter] Fix #339: resize both items when they are fixed size to avoid the change overflowing to the irrelevant Star-sized item by @abdes in #342
  • Refactor: Adaptive Column Width for StaggeredLayout by @Poker-sang in #371
  • fix: Uno Platform - Avoid square border around RangeSelector Thumbs by @MartinZikmund in #400
  • Update DockPanel.md by @mael8 in #419
  • Fix DockPanel measuring bug by @Poker-sang in #416
  • Fix IsNullOrEmptyStateTrigger for Uno to consider FEs as non-empty by @Youssef1313 in #452
  • fix: ProtectedCursor is now supported in Uno Platform by @MartinZikmund in #433

Infrastructure

New Contributors

Known Issues

  • Regression with WAP packaging projects, see: #490

Full Changelog: v8.0.240109...v8.1.240821

v8.1.240606-rc

06 Jun 18:34
efbaf96
Compare
Choose a tag to compare
v8.1.240606-rc Pre-release
Pre-release

What's Changed

Important Notes

  • There should also be a better error message now if the wrong TFM is used by a consuming project:

image

  • We may have noticed issues with the transitive dependencies for the Media packages (or possibly related to Animations package), if you notice issues where you need to install additional packages manually, please comment on this issue.

Highlights

Documentation

Infrastructure

  • Updated actions to latest version for node 20 by @Arlodotexe in #387
  • Fixed duplicate artifact names across matrices in CI by @Arlodotexe in #411
  • Fixed duplicated artifacts in CI when uploading package list by @Arlodotexe in #421

New Contributors

Full Changelog: v8.1.240328-rc...v8.1.240606-rc

For changelog of the last 8.1-rc compared to the last stable release: https://github.com/CommunityToolkit/Windows/releases/tag/v8.1.240328-rc

v8.1.240328-rc

28 Mar 23:53
Compare
Choose a tag to compare
v8.1.240328-rc Pre-release
Pre-release

What's Changed

Welcome to the 8.1-rc release of the Windows Community Toolkit! We have a lot of new and exciting updates in this release, most notably updates for our dependent framework compatibility and a couple of long-standing controls we weren't able to migrate in the original 8.0 release, ColorPicker and TabbedCommandBar, originally contributed by @robloo and @yoshiask.

If you're migrating from 7.x to 8.0, check out our main 8.0 release notes here.

You can find the 8.1.240328-rc packages on NuGet.org.

Migration Notes 📖

We had to update the WinAppSdk TFM to 22621 to resolve incompatabilies with Win2D in the Media component when we upgraded from Windows App SDK 1.3 to 1.4. The full list of notes about this change can be found here, but to summarize:

  • This won't cause issues for targeting older versions of Windows, but it will require those who depend on our packages to upgrade their TFM to net*-windows10.0.22621.0 (where star * is 6.0, 7.0 [support ending soon], or 8.0).

Dependencies/Frameworks

We've updated our packages to support the latest .NET 8.0 (windows10.0.22621.0), Windows App SDK 1.5.240311000, and Uno 5.1.87.

New Components / Features

We've brought over the popular ColorPicker and TabbedCommandBar experiences from our old codebase, enjoy! The Camera helpers have also been fixed for use on Windows App SDK, thanks @GreenShadeZhang for helping us drive understanding on changes in the platform in this space! 🎉

ImageCropper has a new feature thanks to @shatyuka! @Poker-sang added a new Spacing property to DockPanel, and GridSplitter's behavior for fixed columns was updated by @abdes! 🎉

  • Adding ColorPicker by @niels9001 in #241
  • Porting TabbedCommandBar by @niels9001 in #243
  • fix:On the Windows app SDK using CameraHelper, FrameArrived time execution for a period of time will not be triggered. by @GreenShadeZhang in #376
  • Add overlay to ImageCropper by @shatyuka in #364
  • [GridSplitter] Fix #339: resize both items when they are fixed size to avoid the change overflowing to the irrelevant Star-sized item by @abdes in #342
  • [SettingsExpander] Support FontFamily by @niels9001 in #333
  • Enhance: Add spacing properties for DockPanel by @Poker-sang in #346
  • [SwitchPresenter] Sample as a loader replacement by @niels9001 in #285
  • Adding new Segmented sample by @niels9001 in #236

Infrastructure

Ongoing updates/intermediary commits/improvements to the Toolkit's underlying tooling.

Bug Fixes

Other important fixes and updates to AdvancedCollectionView from @Poker-sang and a Layout Cycle issue for the Segmented control by @qhy040404! 🎉

  • Fix: AdvancedCollection inserts at wrong position when adding to end of source collection by @Poker-sang in #309
  • Added missing package descriptions by @Arlodotexe in #362
  • Disable Implicit animations (unsupported) when running under Uno by @Arlodotexe in #326
  • [SettingsExpander] Fix CornerRadius bug by @niels9001 in #329
  • Segmented - Update EqualPanel to avoid Layout Cycle by @qhy040404 in #360
  • Refactor: Adaptive Column Width for StaggeredLayout by @Poker-sang in #371

New Contributors 🎉

Thanks to all our new contributors this release for helping us to improve the Windows Community Toolkit for everyone!

Full Changelog: v8.0.240109...v8.1.240328-rc

If you find any issues with this pre-release, please comment in the discussion and open an issue to let us know.

v8.0.240109

10 Jan 00:04
Compare
Choose a tag to compare

What's Changed

  • [SettingsControls] Bugfix for wrapping states by @niels9001 in #252
  • Fixed compositor nullreference in WinUI 3 by @Arlodotexe in #299
  • Fixing crash when setting empty string for SettingsCard's Header and Description by @Dub1shu in #312
  • [SettingsCard] Accesibility improvements by @niels9001 in #284
  • Fix ExpressionFunctions.ColorLerpRgb by @h82258652 in #304

New Contributors

Misc Updates

NuGet

Full Changelog: v8.0.230907...v8.0.240109

v8.0.230907

07 Sep 18:24
Compare
Choose a tag to compare

See More Information in Release Blog Here

New Package Structure & Breaking Changes 🚨

If you've been following our previous blogs, you know we've made changes to how namespaces and packages work with 8.0.

We've restructured many packages for a few reasons, but the main benefit is it allows developers targeting or migrating between multiple platforms to easily migrate code written on 8.0 without having to change their source. It also enables library developers to multi-target components with XAML easily.

One namespace to rule them all 💍

Regardless of which new features and packages you use (see below), the namespaces for code within the packages are now unified with a root of CommunityToolkit.WinUI.*. This ensures that if you target multiple platforms or migrate between them, no code referencing the Toolkit needs to change (just the package)!

Package Naming 📦

Previously, starting with 7.x, UWP packages started with Microsoft.Toolkit.Uwp.UI.* and had similar namespaces, and WindowsAppSDK package started wih CommunityToolkit.WinUI.UI.* and had a similar namespace. See this blog for more information on our package identity journey. These packages will be deprecated and point to their 8.0 equivalents (continue reading).

There are now two sets of packages for each component:

  • CommunityToolkit.Uwp.* for UWP + WinUI 2 or Uno.UI
  • CommunityToolkit.WinUI.* for Windows App SDK + WinUI 3 or Uno.WinUI

Regardless of the package chosen, as mentioned above, all namespaces have converged on CommunityToolkit.WinUI.* (note the dropping of the additional .UI. in namespace and package names).

If you're using Uno Platform, the same package can be used across your various platform heads now! Just be sure to select the package that corresponds to the target of your Windows platform head, either .Uwp. or .WinUI. for the Windows App SDK corresponding to Uno.UI and Uno.WinUI, respectively.

Removed Features 🦴

The Toolkit is huge! It's had a lot of features added over the course of the last 7 years. Unfortunately, this means we couldn't migrate everything in this initial transition. Also, some features may not be available on all platforms due to platform limitations or unimplemented APIs.

Our initial focus has been on UWP and Windows App SDK compatibility, followed by Web Assembly (WASM). If you find an issue on a particular platform, please let us know, but we may defer you to the underlying platform's repository if an API is missing.

If there's a feature from the Toolkit that wasn't migrated (and not listed below), open a discussion to garner support for future migration or to get information on contributing to migrate it for everyone.

The following is a partial list of known things which are not included in this release:

Migration Notes 🚚

Be sure to read the rest of the breaking change notes above! 😉

Most UI controls have their own package now under CommunityToolkit.<Uwp|WinUI>.Controls.*; we're working to have a meta package again, but do not have one at this time.

For individual grouped control packages of 7.x, you can find the following changes:

  • From Controls.Core:
    • DropShadowPanel has been replaced with Attached Shadows in the Extensions and Media packages.
    • InAppNotification is now the StackedNotificationsBehavior for WinUI's InfoBar in the Behaviors package.
    • Menu is part of WinUI now, see MenuBar.
    • RadialProgressBar is part of WinUI's ProgressRing now, IsIndeterminate="False".
  • From Controls.Layout:
    • Expander is part of WinUI now.
    • GridSplitter is part of the Sizers package, it's also been entirely re-written, but with defaults should look/behave the same, if not better!
    • "Headered" controls are part of the HeaderedControls package, HeaderedItemsControl now uses ItemsPresenter's Header and Footer new, Orientation has been removed, customize the ItemsPanel instead.
  • For parts of the Uwp/WinUI and Uwp/WinUI.UI packages, look for our Collections, Converters, Extensions, Helpers, and Triggers packages.

Other controls either have their own package or have not been migrated yet. Search and then open a discussion if you need assistance.

Packages/Feature Overview 📦

Search for either CommunityToolkit.Uwp or CommunityToolkit.WinUI (Windows App SDK), depending on your target platform, and one of the packages listed below should appear. Today's release is version 8.0.230907.

Read more

v8.0.230828-rc

29 Aug 02:30
Compare
Choose a tag to compare
v8.0.230828-rc Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: v8.0.230823-rc...v8.0.230828-rc

Discuss this release on the prior discussion here

v8.0.230823-rc

23 Aug 23:29
a4ec2ac
Compare
Choose a tag to compare
v8.0.230823-rc Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: https://github.com/CommunityToolkit/Windows/commits/v8.0.230823-rc