Windowstemplatestudio: Question: Confused from libraries used

[msavazzi]

I was studying around and discovered WinTS uses https://github.com/windows-toolkit/WindowsCommunityToolkit and that in the toolkit what is recommended is to use the WCT MVVM implementation and they even provide info on how to migrate from MVVMLight
https://github.com/windows-toolkit/MVVM-Samples/blob/16b5e52f405f92a79f9956d9260233880bd1c89a/docs/mvvm/MigratingFromMvvmLight.md

Also in other topics I've read that WCT is alternative to MahApps.Metro.
But in the MD I read both are used so I'm a little confused.

Can anyone help what is the correct approach and libraries?

Thanks
M

[mrlacey]

The MVVM Toolkit is part of the Windows Community Toolkit (WCT) but is currently in preview.
When it comes out of preview, support will be added to Windows Template Studio (WinTS). (It's already there in the nightly previews if you want to try it out.)

WCT provides a number of controls and helpers for use in UWP and Win32 apps.

MahApps.Metro is used to provide some controls and the general styling in WPF apps generated by WinTS. This is to give apps generated by WinTS a modern looks and feel.

It's perfectly possible to use both MahApps .Metro and WCT in a single WPF app.

---

in the toolkit what is recommended is to use the WCT MVVM implementation

Can you link to where this is recommended?

[msavazzi]

@mrlacey thank you, very clear.

Here:
https://github.com/windows-toolkit/MVVM-Samples/tree/16b5e52f405f92a79f9956d9260233880bd1c89a

This library was inspired by MVVMLight by Laurent Bugnion. Development was started in April 2020 as a path forward for developers using MVVMLight. We've worked with Laurent, the community, and Windows Template Studio to ensure successful migration paths for projects using MVVMLight today.

We decided to start from the ground-up as a new project to architect a modern .NET Standard starting point as well as targeting a high-performance implementation which reduces overhead for memory and CPU cycles. Many things in the .NET ecosystem have evolved and changed since the time MVVMLight had begun.

and reinforcing the concept here:
https://xamlbrewer.wordpress.com/2020/11/16/a-lap-around-the-microsoft-mvvm-toolkit/
https://github.com/windows-toolkit/MVVM-Samples/blob/16b5e52f405f92a79f9956d9260233880bd1c89a/docs/mvvm/MigratingFromMvvmLight.md
https://github.com/windows-toolkit/MVVM-Samples/blob/master/docs/mvvm/MigratingFromMvvmBasic.md

[sibille]

@msavazzi, I'm closing this isssue, please reopen if you have any follow up questions.