Windowscommunitytoolkit: [Question] will controls/xaml UI stuff in this repo be rewritten in WinUI 3.0?

[HppZ]

if it will be, then those controls are available in both c++ & c#, which is great.

[michael-hawker]

Hi @HppZ,

The toolkit controls will still be separate from WinUI.

We don't depend on WinUI at the moment. That's been something open to discussion lately, though it has larger ramifications with WinUI 3.0, so when more info about that is available we'll decide on that point.

However, if we take a dependency on WinUI 3.0, it just means we'll have the same requirements as WinUI for the Toolkit. It doesn't change the behavior between C# and C++ today.

You can include some of the toolkit things in C++ in a round-about way today, but it still requires pulling in the .NET Framework as a dependency.

[HppZ]

thanks for your replying.

I suggest let WinUI do the UI/Xaml work and this WindowsCommunityToolkit focus on other toolkit work (common developer tasks).

[mdtauk]

I see the Community Toolkit as a staging ground for controls that may eventually end up in WinUI, but also as an extra package of utilities, controls, and helpers that make it easier for certain Devs to get things done

[Kyaa-dost]

Closing this issue as it was discussed and answered by the community.

[michael-hawker]

Also wanted to link to #3106 which is the issue tracking making a version of the Toolkit which works on top of WinUI 3.