Decision between Module and User Control

Topics: Prism v4 - WPF 4
Apr 15, 2011 at 10:07 AM

I have a Newsticker component to build in my PRISM application.

Should this be a module or a user control?

I feel that with the minimal functionality it comes with it could be a user control in the Shared library.

Any other decision making tips I cn have to make a call?


Apr 15, 2011 at 2:53 PM
Edited Apr 19, 2011 at 4:53 PM


That decision could be based on your personal preference. A module is generally a set of components grouped by functionality, that together represent a set of related concerns (more information in this chapter of the Prism MSDN documentation).

If you consider that it could be helpful to isolate the Newsticker functionality in a separate functional unit of your application, then it might be suitable for you to place it in a separate module. On the other hand, if you consider that the Newsticker could be coupled with other components without causing problems to your architecture, then it might not be worth the overhead.

I hope you find this helpful.

Guido Leandro Maliandi