WCT Project Reunion 0.5/0.8 Release

[michael-hawker]

See Release Blog here: https://devblogs.microsoft.com/ifdef-windows/windows-community-toolkit-for-project-reunion-0-5/

Use this discussion to discuss anything about the release, if you're having trouble or think you've found an issue. Let us know!

Update the 7.0.3 NuGet packages for CommunityToolkit.WinUI.* have been shipped to support Windows App SDK v0.8.

[Kearsoft]

[azchohfi]

I believe you are trying to get the new Microsoft.Toolkit.Uwp.UI.Animations, which now is CommunityToolkit.WinUI.UI.Animations. The Animations package is from the root of the UI namespace, not inside Controls.

[Kearsoft]

Ho nice! Thanks

[azchohfi]

This seems to be out in the branch:
https://github.com/windows-toolkit/WindowsCommunityToolkit/blob/852102c0f1fc83aeacb0f2995f0cd0129c9b325e/CommunityToolkit.WinUI.UI.Animations/ConnectedAnimations/Connected.cs#L186

[Kearsoft]

Ok I find ... sorry ! Time to stop for today loll :)

[crramirez]

Hello,

I used to share the XAML between UWP and WinUI 3 desktop. With the namespace change, I cannot do it anymore. Do you have any solution for this?

Regards,
Carlos

[crramirez]

Anyone?

[azchohfi]

I don't believe there is a way to alias a namespace in UWP Xaml. There is probably a way thru some MSBuild magic (copy files elsewhere and replace namespaces), but I don't think it would be that simple.

[crramirez]

Ok, thank you. I will double-check the XAML Controls Gallery approach that replaces the .cs files on the fly. Let's see if it works for .xaml ones.

[michael-hawker]

@crramirez hadn't seen the Controls Gallery approach, curious to know about that and if you had luck.

I know @ebariche and @jeromelaban are looking at a tool to help libraries auto-convert: https://github.com/unoplatform/winui3-convert but I think you're talking at the app-level, eh?

[jeromelaban]

Having both targets (WinUI3 and UWP) available in the same solution is not really a target for the converter tool, unfortunately.

One possibility is having a shared project for all shared code, then make XAML files conditional in the shared project, based on a property defined on each project. That would mean having two sets of XAML files (and possibly C# files as well).

[giraudremy]

Hi,

Does CTW 7.0.1 is compatible with the new release 0.5.5 of ProjectReunion ?
When I reference CTW 7.0.1 to my project I have this error on runtime :

Exception thrown at 0x7761A6E2 (KernelBase.dll) in GameClient.WinUi.exe: WinRT originate error - 0x802B000A : 'XAML parsing failed.'.
Exception thrown at 0x7761A6E2 (KernelBase.dll) in GameClient.WinUi.exe: WinRT originate error - 0x802B000A : 'Cannot deserialize XBF metadata property list as 'Icon' was not found in type 'Microsoft.UI.Xaml.Controls.NavigationViewItem'. [Line: 11 Position: 6]'.
Exception thrown: 'Microsoft.UI.Xaml.Markup.XamlParseException' in WinRT.Runtime.dll
WinRT information: Cannot deserialize XBF metadata property list as 'Icon' was not found in type 'Microsoft.UI.Xaml.Controls.NavigationViewItem'. [Line: 11 Position: 6]
XAML parsing failed.

The application can't find the Icon of NavigationViewItem
If I remove reference, the application start and the icon is showing.

Thank for reply

[michael-hawker]

@giraudremy this sounds like this issue: #3950

Try re-creating the project? If you can comment on the issue with any other details, that'd be a great help. Thanks!

[michael-hawker]

FYI @giraudremy we have shipped a 7.0.2 package which supports reunion 0.5.6 and 0.5.7.

[seanocali]

Is there or will there be a release of the toolkit that works with UWP projects that target Microsoft.UI.Xaml instead of Windows.UI.Xaml?

[michael-hawker]

We only support WinUI 3 Desktop apps with our CommunityToolkit.WinUI packages. For UWP development we recommend sticking with UWP + WinUI 2.x and our Microsoft.Toolkit.Uwp packages.

If you need some new C# language features in your UWP app, please see this blog. Otherwise, is there another reason you're trying to build a WinUI 3 UWP app?

[giraudremy]

Hello,

The new stable version of Project Reunion 0.8 has just been released, is there a version of WCT compatible with it?
I actualy test with 7.0.2, but I have lot of exception because AcrylicBacgroundSource have been remote to Project Reunion...

WinRT originate error - 0x80131522 : 'Could not load type 'Microsoft.UI.Xaml.Media.AcrylicBackgroundSource' from assembly 'Microsoft.WinUI, Version=3.0.0.0, Culture=neutral, PublicKeyToken=de31ebe4ad15742b'.'.

[azchohfi]

It has just been released. Update to 7.0.3 and you should be good!

[giraudremy]

Thank, all is good now 👍

[robhurry]

Is there or is there planned support for C++ WinUI 3 Desktop apps with the community toolkit? These of course do not reference the net 5.0 framework so adding the nuget package fails so iuæm not sure if this a reasonable expection or even something that would be possible.

[michael-hawker]

@robhurry the Toolkit is geared towards .NET developers as we're a using the .NET class library. In the past we've heard most C++ developers don't want to pull in the .NET engine to their C++ app in order to use the Toolkit controls, but we have seen a lot more requests for it and have issues tracking it #4044 and #3704.

I have a sample for UWP with C++/WinRT that I should hopefully be publishing soon, but I haven't investigated how it translates to WinUI 3 yet (it should be hopefully easier?). You should theoretically be able to create a C# based Windows Runtime Component for the Windows App SDK, and reference the Toolkit via that to include in a C++/WinRT based app.

[robhurry]

@michael-hawker Great thanks! The sample certainly provides a good starting point. I tried to use the same approach with WinUI but haven't managed to get it work (Even just using any control from a plain C# based Runtime Component in a WinUI C++ application). It builds (After following a similar approach as in the C++WinRt sample) but throws a file not found exception (about the the DLL file of the component which in my understanding does not exist and is not required because there is the winmd file) when trying to Load the WinMD file. Anyway long story short a sample showing how to use the Toolkit with WinUI 3 and the Windows App SDK would be incredibly helpful and appreciated!

[terrycox]

What's the plan for the Toolkit to work with Windows App SDK 1.0 experimental?

[michael-hawker]

We're waiting for WinUI 3 to support the WinUI 2.6 styles as we just updated to reference those. Once WinUI 3 releases a preview or stable build with support for those, we'll release an updated version of the Toolkit packages for it.

Until then our current version is for the 0.8 release as per the WinUI release notes.

[terrycox]

Thanks. Please keep us informed.

[SolidRockProgrammer]

Is there a Windows Community Toolkit (WCT) that will work with Project Reunion 0.8.2?

[michael-hawker]

Our latest existing WinUI packages should work fine with 0.8.2, are you experiencing an issue?

We don't have support for their latest 1.0-experimental release; we're currently waiting for a future 1.0/preview release of WinUI 3 to include the updated WinUI 2.6 styling. We'll ship one when they do with our 7.1 preview or upcoming stable bits depending on timing.

[SolidRockProgrammer]

The issue I'm having is I can install Microsoft.Toolkit.Uwp.UI.Controls 7.0.2

But I can not install Microsoft.Toolkit.Uwp.UI.Controls.DataGrid 7.0.2

Severity Code Description Project File Line Suppression State
Error NU1202 Package Microsoft.Toolkit.Uwp.UI.Controls.DataGrid 7.0.2 is not compatible with net5.0-windows10.0.19041 (.NETCoreApp,Version=v5.0). Package Microsoft.Toolkit.Uwp.UI.Controls.DataGrid 7.0.2 supports: uap10.0.17763 (UAP,Version=v10.0.17763) HardwareSupplies3 C:\Users\me\Source\repos\HardwareSupplies3\HardwareSupplies3\HardwareSupplies3.csproj 1

[crramirez]

@SolidRockProgrammer the NuGet packages and namesoaces are different for WINUI 3. You must use CommunityToolkit.WinUI.* ones.

Check this article: https://devblogs.microsoft.com/ifdef-windows/windows-community-toolkit-for-project-reunion-0-5/

Regards,
Carlos

[SolidRockProgrammer]

Thanks, that fixed my problem

[rick-palmsens]

1.0.0-preview1 was released, can we expect a version of the toolkit that works with the preview?

[michael-hawker]

We're currently working and waiting on our dependencies to update to this version and evaluating if we can release a preview which supports it in some fashion.

[dylech30th]

now they've released preview2 with windows 11 style capability, are we going to expecting the version for the WAS preview 2 in the incoming days?

[edoust]

Would be really nice to have a preview build soon :)

[pellea]

And it would be nice to have a version compatible with .NET 6 RC

[michael-hawker]

@pellea we don't control what version of .NET to run on for WinUI 3. The WASDK is shipping on .NET 5 stable. Once they support .NET 6, we can update our packages built on WinUI 3 to also support .NET 6.

[seanocali]

fdb22f2

[michael-hawker]

Yup, we're just finalizing our 7.1.1 hotfixes now which should be done soon and will release new UWP and WinUI 3 versions shortly.

[michael-hawker]

Hey all!

We've shipped 7.1.1-preview3 for the WindowsAppSDK 1.0-preview3! 🎉🎉🎉

Discussion Topic Now here: #4350
Release Info here: https://github.com/CommunityToolkit/WindowsCommunityToolkit/releases/tag/winui-7.1.1-preview3