CODEWITHSUNDEEP
wpfxamlmvvmuser-controlscaliburn.micro
Loreno
Loreno

Reputation: 668

Caliburn.Micro - why uses UserControl instead of Window

My question is exactly like in the title. I'm starting with Caliburn.Micro for MVVM approach (which also is new for me) and in every tutorial the first step is to remove the default MainWindow.xaml file and create a new UserControl file. Why is that? UserControl does not even accept a Title. Isn't it possible to build application using normal Windows? I already tried that, but with every launch I get error "Cannot find view for ViewModel", although both MainView.xaml and MainViewModel.cs are present. When I created a pair of USerControl and ViewModel for it, everything started to work as expected. So again, why Windows don't work? It wouldn't really be a problem, but I'm thinking that some additions like Modern UI themes for WPF might not work without a window. I'm not sure of that.

Probably one solution would be to display a defined UserControl View inside of a Window, but it's just a workaround.

Upvotes: 0

Views: 767

Answers (1)

mm8
mm8

Reputation: 169200

You could create your own custom shell window by creating a custom WindowManager:

public class CustomWindowManager : WindowManager
{
    protected override Window CreateWindow(object rootModel, bool isDialog, object context, IDictionary<string, object> settings)
    {
        Window window = new Window();
        window.Title = "custom...";
        return window;
    }
}

...that you register in your bootstrapper:

public class HelloBootstrapper : BootstrapperBase
{
    ...

    protected override void Configure()
    {
        _container.Singleton<IWindowManager, CustomWindowManager>();
        ...
    }
}

Upvotes: 1

Related Questions