CommunityToolkit
WinUI libraries should support down to 17763 (1809)
Describe the problem
Looks like with ProjectReunion originally only down to 18362 was supported, so that's what we used for our CommunityToolkit.WinUI packages. However, with the change and release of 1.x of the WindowsAppSDK down to 17763 is supported.
We just never noticed this change and aligned our packages. We should do this as we still should plan to support the 17763 LTS version for a bit until the new LTS version gains traction.
This would help us with labs as well for using Toolkit dependencies as we would like to be consistent on 17763 there as well. We should look into a 7.1.3 release with this change.
Describe the solution
Adjust the min version of our WinUI branch to 17763.
Requires updates to our dependencies:
- [ ] ColorCode [Status: our repo, code updated, need to ship binaries] https://github.com/CommunityToolkit/ColorCode-Universal/pull/26
- [ ] Win2D https://github.com/microsoft/Win2D/issues/886
- [ ] XAML Behaviors https://github.com/microsoft/XamlBehaviors/issues/233 - PR: https://github.com/microsoft/XamlBehaviors/pull/234
Alternatives
No response
Additional info
@azchohfi see any concerns or issues with this?
Help us help you
Yes, but only if others can assist.
Hello, 'michael-hawker! Thanks for submitting a new feature request. I've automatically added a vote 👍 reaction to help get things started. Other community members can vote to help us prioritize this feature in the future!
We'll want to update to .NET 6 and the latest 1.1.4 WindowsAppSDK package.
Right now the following dependencies have 18362 (19H1) as a minimum:
- ColorCode
- XAML Behaviors
- Win2D
XAML Behaviors and Win2D have shipped. So we should be good to update our version in the pipeline once we update ColorCode for ourselves.
This has been blocked by https://github.com/CommunityToolkit/ColorCode-Universal/issues/28 - something changed in the environment the CI runs and we can't build. I have been unable to find any information on the issue...