What is Prism for WPF?

I've come across something called Prism a lot recently. Microsoft, who run the project, describe it as

>Guidelines for composite applications in WPF and Silverlight.

Even after reading the more detailed descriptions out there, I have next to no clue what it's actually about, I'm afraid.

I'm hoping here that someone could give me a clear succinct explanation of what Prism actually is and why I should learn it. I have been a WPF developer for a couple of years now, used MVVM my fair share, and have lately encountered people using Prism, but personally feel a bit out of the loop here.

In particular, I'm wondering about the following points:

• Is Prism literally just (or mainly) a booklet, as given on the MSDN site? Does it include any libraries, if so for what exactly?

• Is Prism an MVVM framework? Should I be using it as the "official Microsoft MVVM framework" over others out there or my own?

• Does it provide dependency injection? Does it relate to MEF at all in this way?

• Anything else I should know about what Prism does, as a WPF/Silverlight developer.

Prism is the Microsoft Patterns and Practices Team official guidance for building "composite applications" in WPF and Silverlight.

Its intended to provide guidance on the best practices for building large scale applications which are flexible in terms of development and maintainability.

This includes guidance on dependency injection (via Unity or MEF), layout (including using MVVM), composite event handling, etc.

---

> Is Prism literally just (or mainly) a booklet, as given on the MSDN site? Does it include any libraries, if so for what exactly?

It is a book, but also includes the libraries for support (on the GitHub site).

> Is Prism an MVVM framework? Should I be using it as the "official Microsoft MVVM framework" over others out there or my own?

Yes and no. It includes guidance for using MVVM, but is far more than an MVVM framework. It's really not, in and of itself, an "MVVM framework" - though it does include MVVM guidance.

> Does it provide dependency injection? Does it relate to MEF at all in this way?

Yes. It originally included Unity, but the latest release includes using MEF for DI.

> Anything else I should know about what Prism does, as a WPF/Silverlight developer.

It's worth taking a look at how they do things. They have a very elaborate "region" concept, as well as good event aggregation support. It also includes good practices for developing against WPF, Silverlight, and Windows Phone simulataneously.

It's a framework for building WPF and Silverlight apps.

http://compositewpf.codeplex.com/

It used to be called "Prism" before Microsoft renamed it to "CompositeWPF."

Answers:

1. Prism is an MVVM framework to use as a foundation for your applications

2. I suggest so depending on your specific requirements. You should post another question with specific details so you can get some specific answers.

3. Prism uses dependency injection (Unity) but does not "provide" it

4. Imo, Prism provides a lot of functionality but is heavy on the learning curve. For small projects with you as the sole developer, you may not need the abstraction and tools that it provides.

A more contemporary answer of what Prism is, is answered on the Github home page.

> Prism is a framework for building loosely coupled, maintainable, and > testable XAML applications in WPF, Xamarin Forms, Uno Platform and > WinUI.

To elaborate, Prism is a collection of libraries to aid in implementing enterprise applications following Microsoft recommended best practice design and architectural patterns.

Prism consists of the following Nuget packages:

• Prism.Core
• Prism.Wpf
• Prism.Forms
• Prism.Uno

Prism supports different DI (Dependency Inversion) / IoC (Inversion of Control) techniques and libraries. It ships with the Unity library for dependency injection, with additional IoC helper functions and classes.

Some of the areas the libraries address:

• Decoupled Event messaging and handling
• Command
• View Model Navigation
• INotifyPropertyChanged implementation
• Dependency Injection

Prism is part of the .NET Foundation.

You may be interested in looking at the Windows Community Toolkit, which follows many of the same principles and patterns adopted by Prism.