Namespace CommunityToolkit.WinUI.Controls Not Accessible in Recent Versions

[MaKrotos]

Describe the bug

In the recent versions of the CommunityToolkit.WinUI library, I've noticed that the namespace CommunityToolkit.WinUI.Controls is not accessible. This causes compilation errors when using the following directive:

using CommunityToolkit.WinUI.Controls;

Additionally, the namespace is not available in XAML when using xmlns:controls="using:CommunityToolkit.WinUI.Controls".

Steps to reproduce

Update the project to the latest version of CommunityToolkit.WinUI.

Try using the namespace CommunityToolkit.WinUI.Controls.

Compilation will fail, indicating that the namespace is not accessible.

Attempt to use the namespace in XAML with xmlns:controls="using:CommunityToolkit.WinUI.Controls".

Observe that the namespace is not accessible in XAML.

Expected behavior

The CommunityToolkit.WinUI.Controls namespace should be available for use without any compilation errors in both C# and XAML.

Screenshots

No response

Code Platform

• [ ] UWP
• [x] WinAppSDK / WinUI 3
• [ ] Web Assembly (WASM)
• [ ] Android
• [ ] iOS
• [ ] MacOS
• [ ] Linux / GTK

Windows Build Number

• [ ] Windows 10 1809 (Build 17763)
• [x] Windows 10 1903 (Build 18362)
• [x] Windows 10 1909 (Build 18363)
• [x] Windows 10 2004 (Build 19041)
• [x] Windows 10 20H2 (Build 19042)
• [x] Windows 10 21H1 (Build 19043)
• [x] Windows 10 21H2 (Build 19044)
• [x] Windows 10 22H2 (Build 19045)
• [ ] Windows 11 21H2 (Build 22000)
• [ ] Other (specify)

Other Windows Build number

No response

App minimum and target SDK version

• [ ] Windows 10, version 1809 (Build 17763)
• [x] Windows 10, version 1903 (Build 18362)
• [ ] Windows 10, version 1909 (Build 18363)
• [ ] Windows 10, version 2004 (Build 19041)
• [ ] Windows 10, version 2104 (Build 20348)
• [ ] Windows 11, version 22H2 (Build 22000)
• [ ] Other (specify)

Other SDK version

No response

Visual Studio Version

2022

Visual Studio Build Number

No response

Device form factor

Desktop

Additional context

No response

Help us help you

Yes, I'd like to be assigned to work on this item.

[ahmedosama007]

Try to update the target framework to 22621

<TargetFramework>net8.0-windows10.0.22621.0</TargetFramework>

From the release notes of version v8.1.240328-rc

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. 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).