MVVM Template uses Community Toolkit by default

[haslingerm]

Describe the bug

Running dotnet new avalonia.mvvm -n Foo I get the 'Community Toolkit' version instead of the 'ReactiveUI' version.

To Reproduce

Create a new solution with the template without specifying which mvvm framework to use.

Avalonia Templates version

11.3.0

Avalonia version

11.3.0

Additional context

According to the docs and the readme in this repo, the avalonia.mvvm template should create the 'ReactiveUI' version by default.

I don't mind either way and not sure if this is a docs or a template issue, but I would like to know which of the two versions is now considered the 'default' for beginners.

[maxkatz6]

Documentation should be updated

[Molenfeuer]

Hello! I think my topic fits here:
I have a similar problem as haslingerm!

On page Music Store App > Create a New Project you say

Leave the MVVM Toolkit option as (the default) ReactiveUI framework.

But this is how my default looks like:

So in my case the "default" is actually "Community Toolkit". I was frustrated because I following the Building Engaging Cross Platform Applications using Rider and Avalonia Video tutorial and he referenced your docs (26:59) and I was wondering why this ... you know... won't work :D I'm deadly new to WPF like UI creation.