New Post: Using Unitybootstrapper in WinForms

I too have the same issue.

Our company are developing new modules. Each of those modules are developed in WPF and have a standalone version.

Although those modules can also be called inside a VB6 and/or Windows Forms interface.

So we have created wrappers for the VB6 part with host the module in a Windows Forms control.

We made sure that the bootstrapper gets called in order for PRISM to initialize correctly.

The WPF interface loads correctly but the no interface are displayed in the regions probably due to the same issue described below.

I don't feel comfortable to modify the IsInDesignMode property since i beleive that it must have good reasoning to have implemented it this way. Also i see that Application.Current is used elsewhere also...

Would it be possible to address this issue in the next release or is it impossible to do?

Edit: In other word does having Application.Current == null (due to the fact that the we're in Windows forms) a show stopper for using PRISM?

Thanks.

Slick