Rename to .NET Community Toolkit

[jaigak]

Since WCT is .NET only and some stuff works on other platforms like Uno, consider renaming to .NET Community Toolkit

[ghost]

Hello Jaiganeshkumaran, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[Kyaa-dost]

@Jaiganeshkumaran Will be closing this issue since there is an issue open regarding this topic #3183

Please feel free to post there whenever you get a chance.

[michael-hawker]

@Kyaa-dost this is about the project as a whole, not just the sample app, so I don't think this is a duplicate?

[Kyaa-dost]

Ok please disregard that @Jaiganeshkumaran. Will leave this open for discussion.

[Kyaa-dost]

Will be moving this to the discussion as that will our new platform for the discussion that still requires further input and clarity.

[jaigak]

I can't accept WCT misleading developers by claiming it's for Windows apps while in reality it's only for Windows apps using .NET. There's a big difference between them. At least mention it in the description that it only works with .NET

[michael-hawker]

We very clearly in all our descriptions call out that we are for .NET projects and part of the .NET foundation:

[jaigak]

You say "building UWP and .NET apps" instead of ".NET based UWP and other .NET apps"

[wutipong]

does WCT currently work with WIN32 (for example) via UWP XAML hosting (XAML island?) ?

[michael-hawker]

Yes, our version 7.0 controls should work in XAML Islands scenarios, though most of the platform team is currently working on WinUI 3 (see notice here); so if you're whole app would be an Island, I'd suggest looking at WinUI 3 Desktop. You can find out more at https://aka.ms/wct-winui3

[wutipong]

so then name the WCT "Windows Community Toolkit" is in a way not entirely misleading, don't you think :).

[michael-hawker]

We've published a blog with an update about our organization and creation of a .NET Community Toolkit: https://devblogs.microsoft.com/ifdef-windows/welcome-to-the-community-toolkit/

The Windows Community Toolkit will still exist and we'll continue to support UWP for the time being and ship equivalent packages for the Windows App SDK.