Question 1

How to pass parameters from a Blazor component to a view model in MvvmBlazor?

Accepted Answer

Declare parameters in both the component and view model with the [Parameter] attribute. MvvmBlazor automatically populates them during the component lifecycle, supporting cascading parameters and type conversion for strong types, as explained in the Parameters section.

Question 2

MvvmBlazor vs using StateContainer in Blazor – which is better?

Accepted Answer

MvvmBlazor is better for complex state management with full MVVM patterns, offering automatic bindings and lifecycle integration. StateContainer is simpler for shared global state but lacks structured view models and automatic UI updates.

Question 3

Can I use MvvmBlazor with Blazor WebAssembly?

Accepted Answer

Yes, MvvmBlazor supports both Blazor WebAssembly and Blazor Server. Set it up by adding services.AddMvvm() in the Startup class, as per the getting started guide.

Question 4

How to handle disposal of resources in MvvmBlazor view models?

Accepted Answer

View models are disposed automatically by Blazor's dependency injection when the component is disposed. Implement IDisposable in the view model for custom cleanup, leveraging scoped service lifetimes.

Question 5

Is MvvmBlazor suitable for large enterprise applications?

Accepted Answer

Yes, its structured MVVM approach, DI integration, and automatic updates support scalability. However, ensure your team tolerates the source generator quirks and .NET 6+ requirement.

Question 6

How to bind to a collection in MvvmBlazor without ObservableCollection?

Accepted Answer

For automatic UI updates, you must use collections implementing INotifyCollectionChanged, like ObservableCollection. Other collections won't trigger re-renders automatically; manual notifications are needed.

MvvmBlazor

What is MvvmBlazor?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions