Until now I've used Silverlight Application Execution Services (AES) for any client-side services (eg Logging, Dialog Management) with MEF metadata for modularity and region placement. I'm now moving into an environment where use of PRISM is mandated.
Unfortunately PRISM makes no mention at all of AES.
I like the AES approach of service configuration through App.xaml but PRISM seems to preclude use of these. It relies on the bootstrapper class to do two different things (a) initialise the container needed to support direct injection and (b) set the
root visual. An AES needs (a) to have been done (so concrete service implementations it wraps can be injected) but (b) to not have been done (because services start up before the Application_Startup code executes.
I thought that maybe an AES could create the container such that the bootstrapper ConfigureContainer method could somehow retrieve that container that an already-running AES has initialized rather than call base.ConfigureContainer, but I suspect this will
break the underlying PRISM code which assumes it has created the container and has complete control of it.
Should I just give up on the idea of using Silverlight AES with PRISM? Was it deliberately avoided from the documentation because there was a realisation the two wouldn't play well together?