Question

I have read some articles referring how navigation work with Screen and Conductor<T> in Caliburn.Micro, but they doesn’t seem to match my requirement.

My WPF application has 3 views:

1. When user starts the application, a welcome screen is displayed, and the application would do some startup work in background.
2. When application finishes startup process, it navigates to a list view.
3. When user clicks an item in list view, it enters a detail view

However, when navigating between different views, I need the whole window to be replaced, it seems Conductor<T> works when there is a ContentControl in the view and replaces part of the view, now I need the previous view to be destroyed and a new view replaces it, no ContentControl, no MDI application, so what do I miss to implement this simple navigation?

Thanks

Answer 1

Why can’t this be a ShellViewModel/ShellView with a ContentControl that consumes the entire shell Window? Alternatively, you could look at the WindowManager class provided with Caliburn.Micro.