Hi DRAirey1,

I apologize for the missunderstanding about the Event word in bold, as it would only refer to any Event class in general.

Thank you for deeper desciption of the scenario. One possible way you could perform to solve this issue would be to Publish an InitilizationCompletedEvent for example on the BootStrapper and subscribe to this event on the DirectoryViewModel so it would know that every other ViewModel has already been initialized. Therefore, you could Publish the UriChanged event on the InitializationCompletedEventHandler() method.

In order to Publish the InitializationCompletedEvent, you would need to execute it as always on the overriden BootStrapper's run() method because it would execute right after the Modules initialization according to the BootStrapper's run() order's execution. Then, you would need to Subscribe to InitializationCompletedEvent on the DirectoryViewModel's constructor, in addition to implementing the InitializationCompletedEventHandler from where you would Publish your UriChanged event.

For more information, you could refer to the following disscusion which talks about a similar issue.

• Module initialization problem
  

I hope this helped you.
Regards.

Gabriel Ostrowsky
https://blogs.southworks.net/gostrowsky