Project template

dotnet new install Plugin.Wpf.MVVMExpress.Templates
dotnet new wpf-mvvmexpress -n MyApp
cd MyApp
dotnet test MyApp.Tests

nuget.org: Plugin.Wpf.MVVMExpress.Templates 1.0.0

GitHub Packages: Plugin.Wpf.MVVMExpress.Templates 1.0.0

From the product repo, without installing the nupkg: dotnet new install templates/wpf-app and templates/page, then dotnet new wpf-mvvmexpress -n MyApp.

Same commands from the IDE: install the Visual Studio Code or Visual Studio Marketplace listing. The wrappers install the pack and run dotnet new — they do not copy the scaffold.

Short name: wpf-mvvmexpress. Creates a WPF Frame host on net10.0-windows. There is no Shell.

Demo sign-in is demo@mvvmexpress.dev / secret. Production tokens stay on an IAuthState adapter — do not store them on the ViewModel.

cd MyApp
dotnet new wpf-mvvmexpress-page -n Catalog --namespace MyApp

Creates a XAML page, ViewModel, service, AddCatalog(), and {Binding} / Command. Map the route in App startup:

builder.Services.UseWpfMvvmExpress(o => o
    .UseFrameNavigation((nav, _) => nav
        .Map<LoginViewModel, LoginPage>("login")
        .Map<HomeViewModel, HomePage>("home")
        .Map<CatalogViewModel, CatalogPage>("catalog"))
    .UseDialogs()
    .UseAuth<LoginViewModel>());

builder.Services.AddCatalog();

• Do not reconstruct GuardedNavigator — UseAuth<TChallenge>() already wraps it.
• Register an IAuthState adapter. The template uses an in-memory demo.
• Add Validation, Pagination, or Testing only when the screen needs them — the template already references the host set.
• Playground remains the cloneable 15-minute path if you want the in-repo sample instead of a new project.

Getting started walkthrough: Install and first screen

IDE wrappers: VS Code and Visual Studio extensions