Gabriel,
Thanks for the effort, but I'm afraid we're dealing with a different problem than module initialization. Your solution appears to be promising for controlling the ordering of events for modules, but it doesn't work for regions. That is, after stepping through the debugger, your method of overriding the Run method guarantees that all the modules have loaded, but apparently it doesn't guarantee that the Regions have been loaded. This is the rub: since the loading of viewers into regions is left up to the run-time, there's no accessible event or property that tells us when all the regions have loaded. Theoretically, if you had a view switching application, you could keep loading up regions continuously and there's no real way to say that you're 'done' initializing the regions.
Again I come back to the fact that we need a persistent property on the CompositePresentationEvent<TType> class that gives us the last published value.
Thanks for the effort, but I'm afraid we're dealing with a different problem than module initialization. Your solution appears to be promising for controlling the ordering of events for modules, but it doesn't work for regions. That is, after stepping through the debugger, your method of overriding the Run method guarantees that all the modules have loaded, but apparently it doesn't guarantee that the Regions have been loaded. This is the rub: since the loading of viewers into regions is left up to the run-time, there's no accessible event or property that tells us when all the regions have loaded. Theoretically, if you had a view switching application, you could keep loading up regions continuously and there's no real way to say that you're 'done' initializing the regions.
Again I come back to the fact that we need a persistent property on the CompositePresentationEvent<TType> class that gives us the last published value.