Program architecture with PRISM Modules and MVVM?

I actually like both of your approaches, but which one to use really depends on your requirements. If you want to explicitly have one module tell another module what to do, then service locator is the way to go. However, that approach has the tendency to bring some level of tight coupling across your modules.

I actually like both of your approaches, but which one to use really depends on your requirements. If you want to explicitly have one module tell another module what to do, then service locator is the way to go. However, that approach has the tendency to bring some level of tight coupling across your modules.

If tighter coupling is not what you want (for example, what happens when you add a fourth module that needs to handle the action? ), then the event aggregator can get you the looser coupling. This approach does require a little more rigor and up-front work to manage regions, etc, as it's easy to end up with a somewhat unmanageable set of events that lead to debugging difficulties (I've got that problem now in a project).

Kind of a nebulous answer, but I hope it helps :-) Nate.

Probably not a good idea to mix designs on second thoughts. – TheAfrican Oct 31 at 17:52.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.