Modules vs. Controls

May 28, 2009 at 12:05 AM


I have been working my way through the QuickStarts and have been trying to figure out how to apply these patterns to my own project.

Does anyone know of any good articles on how to break up my application into the correct pieces (modules, controls, regions, views, etc.)?

It seems logical to break my app into functional areas and create modules for each of them. The downside seems to be that you could end up with too many and have a bit of a mess on your hands.

Your thoughts are appreciated.


May 28, 2009 at 6:20 PM

Hi Rick,


It is great that you started to explore Prism-v2 and I hope you are liking it.


A couple of days ago, a similar discussion came up in a thread. Perhaps you might be interested in it:

·         When should we create a module?


Although there are not guidelines on when to create each of these things specifically you might find some recommendation in this articles:

·         Module

·         Shell and View

·         UI Composition


Please let me know if this helps.


Damian Schenkelman

May 30, 2009 at 6:27 PM

Thank you. I found the three links right after my post.

I am now trying to figure out the right data model to use. Most of my data will be pushed from the server using a duplex channel.