Could you please explain to me more detail information regarding your required scenario?

Hi Terry,

We always recommend to keep down the communication simple and use commanding and binding whenever possible. If not, then you can turn to Event Aggregator to establish communication between multiple view-models in loosely coupled way.

Unfortunately, we dropped the EA bits in our ClientUI framework in the first release as the EA was still immature at that time. We're planning to revisit and add the EA bits in the R2 release.

Do you have a preference of EA that works well in your experience? For instances, EA with reactive extension, or EA with messenger-style model, or perhaps a more complicate Prism-style EA?

Let me know, thanks!

Hope this helps,
Jimmy

Hey Jimmy

I did end up implementing a EA using the EA from Prism V2.01, it was very simple to implement and does seem to work well. Having something built into the framework does have its advantages.

Thanks for your quick response

Hi Terry,

That's cool. Yep, you can always use the Prism bit whenever needed. Although having EA built-in will eliminate the need to reference to other unnecessary assemblies, thus saving the bits further.

Thanks,
Jimmy.