Base Class to manage Views

Topics: Prism v2 - Silverlight 3, Prism v2 - WPF 3.5
Feb 3, 2010 at 1:59 AM
Edited Feb 3, 2010 at 1:59 AM

Hi @all,

does it make sense to build something like a base class to switch between different views in a Module? (to handle the resolving, removing and activating of views).

I guess this is more or less always the same in the Modules?!

Maybe a base class for the Controller, which takes care of the Views?




Feb 3, 2010 at 4:50 PM

Hi Manullino,

Having a base controller class can be a very good idea, specially if you have common functionality that is reused across the application, as you reuse the code and write less tests. The common approach is placing this kind of classes in the infrastructure project so they can be referenced from your different modules.

This thread provides some information and a couple of links about managing Views/ViewModels across an entire application, so you might find it useful.

Please let me know if this helps.

Damian Schenkelman

Feb 4, 2010 at 1:41 AM

HI Damian,

thanks for the link, this helps a lot!!

I have the feeling the Screen Factory Pattern is not very common.But I like the idea.

I couldn't find a tutorial, only John Papas post and the Prism Explorer. Do you know other resources?