This project is read-only.
Prism provides the following benefits:
  • Provides support for WPF and Silverlight
  • Dynamically composes user interface components
  • Application modules can be developed, tested and deployed by separate teams
  • Allows incremental adoption
  • Provides an integrated user experience
  • Helps you build applications in WPF and Silverlight that have a single code base

Even single-person projects experience benefits in creating more testable and maintainable applications using this modular approach.

"Prism" is not a port of previous smart client offerings, instead it is a new deliverable that is optimized for WPF and Silverlight. It aims to deliver a simplified approach that is more easily adoptable.

Read what people are saying about "Prism" below.

Team perspective

Customer perspective


The source in the spikes folder are for illustrative purposes only. These will not be part of the final deliverable. The spikes have a dependency on Castle Windsor ("Prism" will not depend on it). Castle Windsor can be downloaded from

Last edited Feb 19, 2009 at 6:42 PM by ndelgado, version 6


ericpizon Feb 20, 2009 at 9:12 PM 
Is this applicable to all layers (service, business logic and data access layers) of a n-tiered architecture? Or is this only application to the presentation layer?

patelsan Jan 29, 2009 at 1:24 AM 
Title contains "Silverlight", it is hardly mentioned anywhere in the overview. Most of the places it mentions WPF. What is the level of support and guidence available for SL. Could anybody please clarify this? I am more interested in Silverlight. Thanks in advance for the clarification.

ibaumann Oct 10, 2008 at 4:09 PM 

The Composite Application Guidance for WPF (Prism) is container agnostic, but the current release comes with out-of-the-box support for the Unity container in the Microsoft.Practices.Composite.UnityExtensions project.

So, you may implement your own container too, if you want to, but you will need to implement a façade for it as shown in Willem Meints blog post: Using Spring.NET as IOC container for Composite WPF

To get the latest release of the Composite Application Guidance for WPF, you must go here:

Hope it helps.

Ignacio Baumann Fonay

davekolb May 23, 2008 at 9:51 PM 
When building a new application shell is there an alternative already built into Prism to having to use the Castle Windsor IoC Container or is it roll your own container if you don't use Castle? Thanks, Dave