WinUI libraries should support down to 17763 (1809)

[michael-hawker]

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] Update Versions to support down to 17763 and Fix CI ColorCode-Universal#26
• Win2D Microsoft.Graphics.Win2D NuGet should support 17763 microsoft/Win2D#886
• XAML Behaviors Microsoft.Xaml.Behaviors.WinUI.Managed should support 17763 microsoft/XamlBehaviors#233 - PR: Lower WindowsAppSDK min version to be 17763 microsoft/XamlBehaviors#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.

[ghost]

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!

[azchohfi]

No concerns.

[michael-hawker]

We'll want to update to .NET 6 and the latest 1.1.4 WindowsAppSDK package.

[michael-hawker]

Right now the following dependencies have 18362 (19H1) as a minimum:

• ColorCode
• XAML Behaviors
• Win2D

[michael-hawker]

Add links to tracking issues on dependencies to original post.

[michael-hawker]

XAML Behaviors and Win2D have shipped. So we should be good to update our version in the pipeline once we update ColorCode for ourselves.

[michael-hawker]

This has been blocked by CommunityToolkit/ColorCode-Universal#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...