Can Prism be used in a Client/Server Architecture?

Topics: Prism v4 - WPF 4
Jul 9, 2012 at 10:05 AM

I'm new to WPF, C#, .NET, Prism, and MVVM.

My company is planning to use the above technologies to build a Client/Server solution for it's new product range.

I have started looking at Prism as a possible framework for the new project. However I'm unclear how the Prism framework would be implemented in a Client/Server architecture.

Based on the MVVM pattern, we envisage that the Client would contain the Views, and View  Models, while the Server would contain the Models and Business logic.

When it comes to a Client/Server architecture like the one described above, is Prism a Client side framework only? Or can the Prism framework also be used on the Server side?

Any help on this topic would be very welcome. Thanks.








Jul 9, 2012 at 8:36 PM

Hi Paul, if the applications you are creating have a database back-end, Prism and MVVM are ideal for that scenario. I would suggest also taking a look at RIA Services ( to get you started creating a service layer that is hosted on the server but available on the client. You don't have to use Prism for this, but if you application needs to be split into modules, then I would use Prism, MVVM and RIA Services.

Jul 10, 2012 at 9:12 PM
Edited Jul 10, 2012 at 9:12 PM

Hi Paul,

As far as I know, Prism only provides guidance about Client side application development. Hence, you could say that Prism is a "Client side framework" only. However, I believe you should be able to use Prism in your client application without problems, as Prism is usually agnostic to the Client-Server communication and business logic of the application.

As a starting point, I believe you could find Pedro's recommendations in the previous response useful.


Damian Cherubini