Prism Module Loading Locks-up Dispatcher Thread. Is There a Way Around This?

Question

The Prism application I have performs multiple startup tasks that can take a while and if some of those tasks fail to execute properly it will make the application functiona

Answer 1

You have (at least) two options:

• use a SplashScreen
• do module initialization on another thread

Splashscreen example:

internal class MyBootstrapper
{
    // [...]
    protected override void InitializeModules()
    {

        var splashScreen = new SplashScreen( "myLogo.png" );
        splashScreen.Show( false );
        try
        {
            base.InitializeModules();
        }
        finally
        {
            splashScreen.Close( TimeSpan.Zero );
        }
    }
}

Tasks example:

internal class MyBootstrapper
{
    // [...]
    protected override void InitializeModules()
    {
        Task.Run( () => base.InitializeModules() );
    }
}

with this, you have to be careful that some services might unexpectedly not be created on the ui thread (e.g. EventAggregator) and those will behave strangely. If that happens, resolve them before kicking off the task that does the initialization.