CODEWITHSUNDEEP
wpfcaliburn.micro
Kelly
Kelly

Reputation: 7183

Caliburn.Micro Starting the bootstrapper from code?

Normally I just but the bootstrapper in the resources of the App.xaml, but for an app I'm building I need code execution to begin elsewhere and then start the bootstrapper up once I'm done my initialization code.

How can I start the bootstrapper?

I set the App.xaml to call a function as then did this:

using System.Windows;

namespace WpfApplication9
{
    public partial class App : Application
    {
        private AdminBootstrapper b;

        private void App_OnStartup(object sender, StartupEventArgs e)
        {
            //DO initialization

            b = new AdminBootstrapper();
            b.Start();
        }
    }
}

When I run nothing happens, and my view does not appear. I know the view/viewmodel work because if I put the bootstrapper in the resources section of the App.xaml it appears.

What am I doing wrong here?

Upvotes: 3

Views: 4502

Answers (3)

John Blacker
John Blacker

Reputation: 149

Use the Initialize() method instead of Start(). I had the same error and searched the internet and found a post that said to use Initialize() instead. I tried it on the sample app in the Caliburn.Micro docs and it worked for me.

Upvotes: 3

Boklucius
Boklucius

Reputation: 1926

Maybe not the correct way (wanted to remove it from the markup) but still, this code seems to work...

public partial class App : Application
{
    MyBootstrapper _bootstrapper;

    protected override void OnStartup(StartupEventArgs e)
    {
        _bootstrapper = new MyBootstrapper();   
        base.OnStartup(e);
    }
}

public class MyBootstrapper : BootstrapperBase
{
    public MyBootstrapper()
    {
        Start();
    }

    protected override void OnStartup(object sender, System.Windows.StartupEventArgs e)
    {
        DisplayRootViewFor<ShellViewModel>();
    }
}

Upvotes: 0

McDonnellDean
McDonnellDean

Reputation: 1087

This is not the "correct" way to use the bootstrapper, the bootstrapper IS the place were you do the setup you talk of. The whole point is to provide a place were Caliburn.Micro knows you are going to set up. Without seeing your bootstrapper though it is impossible to know what is wrong.

The root ViewModel is not loaded until after Configure is called. This is your extensibility point. If you need to do complex configuration you could call a couple of overrides here and then derive a class which exposes these methods.

In general though you would need to provide more information about what you are doing before I could give you a concrete recipe.

Upvotes: 1

Related Questions