Hello,
In order to pass the entire object through Modules, you could use the EventAggregator approach by working on Prism 4.1. As you may see on the EventAggregation QuickStart, this feature would let you communicate between Modules and pass also an object as parameter.
Therefore, for implementing this you may need to first initialize ModuleB in the ModuleA's CommandHandler, so that ModuleB suscribes to the Event that ModuleA would Publish afterwards. And then, ModuleA would Publish the Event from the CommandHandler, passing the ModelA object as parameter to the ViewModel that would handle the event suscription.
Anyway, I would like to point out that new versions of Prism 4.2 and 5 has been released and they resolve the object parameters passing through UriQuery. You may find more information in the Prism 5 MSDN Guide:
I hope this helped you,
Regards.
Gabriel Ostrowsky
https://blogs.southworks.net/gostrowsky
In order to pass the entire object through Modules, you could use the EventAggregator approach by working on Prism 4.1. As you may see on the EventAggregation QuickStart, this feature would let you communicate between Modules and pass also an object as parameter.
Therefore, for implementing this you may need to first initialize ModuleB in the ModuleA's CommandHandler, so that ModuleB suscribes to the Event that ModuleA would Publish afterwards. And then, ModuleA would Publish the Event from the CommandHandler, passing the ModelA object as parameter to the ViewModel that would handle the event suscription.
Anyway, I would like to point out that new versions of Prism 4.2 and 5 has been released and they resolve the object parameters passing through UriQuery. You may find more information in the Prism 5 MSDN Guide:
I hope this helped you,
Regards.
Gabriel Ostrowsky
https://blogs.southworks.net/gostrowsky