Open RebeccaAnne opened 3 years ago
should probably split this out into two issues covering WinUI2 and WinUI3
Hi, we've shipped a new version of the Windows Community Toolkit, see blog here. It makes it easier to use components between WinUI 2 and WinUI 3, like the GridSplitter
you use (it's in the CommunityToolkit.*.Controls.Sizers
packages), but in a consolidated namespace for XAML CommunityToolkit.WinUI.Controls
.
I would suggest you consolidate your namespace similarly for the Uwp and WindowsAppSDK versions of the AdaptiveCard API to make it easier for folks to have a single-source to multi-target the two platforms. There's information in our blog about why we did this as well. Would make it easier if you decide to ship more XAML focused view hosts too in the future.
This seemed to be the main tracking issue for this update of adding support for WinUI 3, so figured it'd make sense to add a comment here vs. creating a new issue?
Note: Updating to WinUI2 will address this accessibility issue: 31569532
EDIT: the accessibility issue has now been resolved. Repurposing this issue to track switching to WinUI 2 and 3