What about renaming PuzzleApplicationBootstrapper in ApplicationBootstrapper?

[micdenny]

or at least adding a shortcut if it's possibile, just because we would like to have the PuzzleApplicationBootstrapper our default easy peasy container, so it could be cool to have it named ApplicationBootstrapper and probably under Radical.Windows namespace.

I saw doing such things in new frameworks out there (like EF7), they use to add the entry point class/methods in the very first namespace where they belong to (eg.: Microsoft.Data.Entity), to avoid searching the right namespace to add, and it could also be great to have extension method to enable different containers, so to have something like:

using Radical.Windows;

var bootstrapper = new ApplicationBootstrapper<Presentation.MainView>();

when using just the internal container (puzzle), or this:

using Radical.Windows;

var bootstrapper = new ApplicationBootstrapper<Presentation.MainView>().UseCastleWindsor();

you see, the same namespace is imported Radical.Windows, and you have only to add the proper nuget package to have in the same namespace the extension method UseCastleWindsor(), so no need to find in other namespace.

how cool could it be? 😄

[mauroservienti]

Very cool. I love it.
Basically we could split the Bootstrapper in at least 2 pieces:

• Application logic bootstrapper
• Container bootstrapper

The container one can be pluggable using the extension methods logic you proposed. I also think that the same approach should be used at the full fx level.

[mauroservienti]

Depends on #23

[mauroservienti]

Moving this back to the ready state since we need #23 before moving on with this