Prism is a framework for building loosely coupled, maintainable, and testable XAML applications in WPF, Xamarin Forms, Uno Platform and WinUI. Separate releases are available for each platform and those will be developed on independent timelines. Prism provides an implementation of a collection of design patterns that are helpful in writing well-structured and maintainable XAML applications, including MVVM, dependency injection, commands, EventAggregator, and others. Prism's core functionality is a shared code base supported in .NET Standard 2.0, .Net Core 3, and .NET Framework 4.5. Those things that need to be platform specific are implemented in the respective libraries for the target platform. Prism also provides great integration of these patterns with the target platform. For example, Prism for Xamarin Forms allows you to use an abstraction for navigation that is unit testable, but that layers on top of the platform concepts and APIs for navigation so that you can fully leverage what the platform itself has to offer, but done in the MVVM way.
Prism 7 is a fully open source version of the Prism guidance originally produced by Microsoft patterns & practices. The core team members were all part of the P&P team that developed Prism 1 through 5, and the effort has now been turned over to the open source community to keep it alive and thriving to support the .NET community. There are thousands of companies who have adopted previous versions of Prism, and we hope they will continue to move along with us as we continue to evolve and enhance the framework to keep pace with current platform capabilities and requirements.
Help Support Prism
As most of you know, it takes a lot of time and effort for our small team to manage and maintain Prism in our spare time. Even though Prism is open source and hosted on GitHub, there are a number of costs associated with maintaining a project such as Prism. Please be sure to Star the Prism repo and help sponsor Dan and Brian on GitHub.
E2E Build Status
- Documentation is maintained in the Prism-Documentation repo under /docs and can be found in a readable format on the website.
- For general questions and support, post your questions on StackOverflow.
- You can enter bugs and feature requests in our Issues.
Videos & Training
By watching our courses, not only do you help support the project financially, but you might also learn something along the way. We believe this is a win-win for everyone.
- Introduction to Prism
- What's New in Prism 5.0
- Prism Problems & Solutions: Showing Multiple Shells
- Prism Problems & Solutions: Mastering TabControl
- Prism Problems & Solutions: Loading Modules Based on User Roles
- Prism Problems & Solutions: Loading Dependent Views
We appreciate your support.
Both Brian and Dan are streaming live on a regular basis covering topics for WPF and Xamarin.Forms developers. Be sure to follow and subscribe to find out when they go live.
Official Prism releases are available on NuGet. Prism also has a MyGet feed which will be updated with each merged PR. If you want to take advantage of a new feature as soon as it's merged into the code base, or if there is a critical bug you need fixed we invite you to try the packages on this feed. Our feed is a public feed in the MyGet Gallery.
https://www.myget.org/F/prism/api/v3/index.json as a package source to either Visual Studio or Visual Studio for Mac.
These are the base packages for each platform, together with the Prism's Core assembly as a cross-platform PCL.
|Cross Platform||Prism.dll||Prism.Core||net45, net47, netstandard2.0|
|WPF||Prism.Wpf.dll||Prism.Wpf||net461, net47, net48, netcoreapp3.1|
|Uno Platform and WinUI||Prism.Uno.dll||Prism.Uno||netstandard2.0 (WebAssembly), xamarinios10, monoandroid90, xamarinmac20, uap10.0.16299|
Each supported IoC container has its own package assisting in the setup and usage of that container together with Prism. The assembly is named using this convention: Prism.Container.Platform.dll, e.g. Prism.Unity.Wpf.dll. Starting with version 7.0, Prism is moving to separate packages for each platform. Be sure to install the package for the Container and the Platform of your choice.
- For developers using Unity with Prism 6, take note that the new Unity maintainer has made major breaking changes. This includes changing namespaces and the package structure. These changes were NOT made by the Prism team nor do we have any control over it. When upgrading to Prism 7 you will need to uninstall the existing Unity package as we now reference the Unity.Container NuGet.
A detailed overview of each assembly per package is available here.
Prism Template Pack
Prism now integrates with Visual Studio and Xamarin Studio to enable a highly productive developer workflow for creating WPF, and native iOS and Android applications using Xamarin.Forms. Jump start your Prism apps with code snippets, item templates, and project templates for your IDE of choice.
Visual Studio Gallery
The Prism Template Pack is available on the Visual Studio Gallery. To install, just go to Visual Studio -> Tools -> Extensions and Updates... then search for Prism in the online gallery:
There are certain things that cannot be added directly into Prism for various reasons. To handle these common tasks such as supporting PopupPage's in Xamarin Forms, there are Prism Plugins. You can find a number of Plugins available on NuGet from our maintainer @DanJSiegel.
- Prism.Plugin.Popups (Forms Only)
Prism.Plugin.Logging (Works on all Platforms)
- Adds support for Syslog, Loggly, Graylog, Application Insights, & App Center
- Adds advanced Container Registration abstractions
- Adds DryIoc ContainerExtension with support for Microsoft.DependencyInjection.Extensions & Splat. Uses a singleton pattern to allow initialization from a native platform
- Provides an extended PrismApplication with additional error handling and platform specifics support for Prism.Forms
For stable samples be sure to check out the samples repo for the platform you are most interested in.
We strongly encourage you to get involved and help us evolve the code base.
- You can see what our expectations are for pull requests here.
This project is part of the .NET Foundation.