Geek asks and answers

Caliburn.Micro: views and boot files in different projects

I play with Caliburn. I have a little problem. I like to have one project for the starter application containing boot files, configuration files, etc. The user interface of the application is then organized in its own project. This works fine with Prism, but it seems to me that the caliber is not like if the user interface and the boot block are separate. Is this right or am I missing something?

edit: I refer to the bootloader in app.xaml. The bootloader currently looks like this:

public class AppBootstrapper : Bootstrapper<MainViewModel>
{
}

ViewModel is in another project, and when the application starts, the application displays "Cannot find the view for the view model ...". This does not happen if ViewModel and View are in the same project as bootstrapper.

+5
source share
1 answer

Override SelectAssembliesin bootloader.

Enabling logging can be useful, CM will tell you the options for the names of the view model or view that it is trying to find:

if (Debugger.IsAttached)
     LogManager.GetLog = type => new DebugLogger(type);

Additional information: Is it possible to create different objects for views, ViewModels and models in one solution

+4
source

More articles:


All Articles