Question 1

How to integrate MVVM Dialogs with Caliburn.Micro?

Accepted Answer

The project provides a dedicated sample repository on GitHub showing integration. You'll need to set up IDialogService in your bootstrapper and use it in view models, similar to the examples provided.

Question 2

Can MVVM Dialogs handle custom dialog windows in WPF?

Accepted Answer

Yes, by implementing the IWindow interface for your custom windows. The library supports this for non-standard dialogs, allowing full control over presentation and behavior.

Question 3

Is MVVM Dialogs compatible with .NET 6 or .NET 7?

Accepted Answer

As a WPF library, it should work with .NET versions that support WPF. Check the NuGet package for specific targets, but given its maintenance status, it's likely compatible with newer .NET frameworks.

Question 4

MVVM Dialogs vs Prism's dialog service for WPF?

Accepted Answer

MVVM Dialogs is a lightweight, focused library for dialog abstraction, while Prism is a full MVVM framework with dialog services built-in. Choose MVVM Dialogs for simplicity or Prism if you need broader framework features.

Question 5

How to unit test view models that use MVVM Dialogs?

Accepted Answer

Mock the IDialogService interface in your tests. Since dialog logic is abstracted, you can simulate responses without UI dependencies, making view models easily testable as emphasized in the README.

Question 6

What are good alternatives to MVVM Dialogs for WPF applications?

Accepted Answer

Alternatives include using built-in dialog services from MVVM frameworks like Prism or MVVM Light, or implementing custom abstractions. MVVM Dialogs is best for dedicated, testable dialog management without framework lock-in.

MVVM Dialogs

What is MVVM Dialogs?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions