The latest source code can be found on the following CodePlex sites:

https://prism.codeplex.com

• Prism.Composition,
• Prism.Interactivity
• Prism.UnityExtensions
• Prism.MefExtensions

https://pnpmvvm.codeplex.com

• Prism.Mvvm

https://pnppubsub.codeplex.com

• Prism.PubSubEvents

Prism.Mvvm and Prism.PubSubEvents are portable class libraries that now target Windows Phone 8.1.

Prism.Mvvm targets:

• .NET framework 4.5
• Windows 8
• Windows Phone 8.1
• Windows Phone Silverlight 8

Prism.PubSubEvents targets:

• .NET Framework 4
• Silverlight 5
• Windows 8
• Windows Phone 8.1
• Windows Phone Silverlight 8

In the process of converting AdventureWorks Shopper to run on Windows Phone 8.1 we spent enough time to test that Prism for Windows Runtime works well with Windows Phone 8.1. We did not spend time making the reference implementation user interface conform to the phone UX standards and navigation standards. We decided it was best to make the library available for Windows Phone 8.1 and universal app development. We also did not stress test our library code specifically on Windows Phone.  The code has been stress tested on Windows Store and for the portable class libraries on WPF.

Prism.StoreApps targets:

• Windows 8.1
• Windows Phone 8.1

Prism.Mvvm targets:

• .NET framework 4.5
• Windows 8
• Windows Phone 8.1
• Windows Phone Silverlight 8

The source code for Prism.Mvvm can be found at https://pnpmvvm.codeplex.com.

Prism.PubSubEvents targets:

• .NET Framework 4
• Silverlight 5
• Windows 8
• Windows Phone 8.1
• Windows Phone Silverlight 8

The source code for Prism.PubSubEvents can be found at https://pnppubsub.codeplex.com.

Check it out and give us your feedback.

• Provide Portable Class Library version of Prism library (where reasonable)
• Address high priority items identified on the CodePlex site.

Providing PCL versions of the MVVM and Event Aggregator projects will help you create companion and/or convergent applications. This release is the first step in supporting these scenarios. We still have work to do before completely supporting these scenarios. I discuss what’s next later in this post. The other advantage is that more platforms can take advantage of improvements we make to the library. For this release we were able to harvest the View Model Locator and BindableBase from Prism for Windows Runtime and add it to the MVVM project. We also integrated the Property Support class Prism for WPF with the BindableBase class making it more functional.

What’s New is Prism 5.0?

When we first created Prism one of the primary goals was to allow you to use the components that you want. For this release we took it a step farther by separating the features into separate assemblies – Prism.Composition, Prism.Mvvm, Prism.PubSubEvents, and Prism.Interactivity.

Prism Assembly

The Prism assembly no longer exists, instead that functionality has moved into the assemblies mentioned above. If you want to use all the Prism functionality, you can download the Prism NuGet package which will download the NuGet packages for Prism.Composition, Prism.Mvvm, Prism.PubSubEvents, and Prism.Interactivity.

Prism.Composition

• Assembly contains the Prism.Logging, Prism.Modularity, and Prism.Regions namespaces. 
• The Prism.Events namespace exists in this assembly but it has been marked as Obsolete because we want you to move to the Prism.PubSubEvent  PCL version of the classes.
• The Prism.ViewModel namespace also exists in this assembly but the NotificationObject and PropertySupport classes are marked obsolete because we want you to move the Prism.Mvvm PCL version of the classes.
• UriQuery class was renamed to NavigationParameters, it keeps the same functionality as before
• NavigationParamaters class can now be used to pass object parameters during navigation using the overloads of the RequestNavigate method of a Region or RegionManager instance. This was a community requested on CodePlex.

Prism.Mvvm

• Portable class library that encapsulates Prism’s MVVM support including DelegateCommand, CompositeCommand, and ViewModel. This allows your view models to be portable across WPF, Windows Phone 8, and Windows Store 8.1.
• Views and view models can be wired together using the new ViewModelLocationProvider’s convention-based approach. View model construction can still be accomplished using a dependency injection container. We migrated the View Model Locator that we developed in Prism for Windows Runtime to the Prism.Mvvm project.
• BindableBase class provides a new implementation of the INotifyPropertyChanged interface. We decided to take BindableBase from the Prism.StoreApps because it already supported CallerMemberName attribute with INPC.
• NotificationObject and PropertySupport classes are marked obsolete in the Prism.Composition assembly. You should use BindableBase instead of NotificationObject and you should use SetProperty to update the property’s backing field when inheriting from BindableBase.
• DelegateCommands are now extendable and provide Async support.
• Execute and CanExecute methods on DelegateCommand are now marked virtual.
• WeakEventHandlerManager is now public

Prism.PubSubEvents

• Portable class library that allows your view model to be portable across WPF, Windows Phone 8, and Windows Store 8.1.
• EventAggregator classed moved to this library

Prism.Interactivity

• Prism Interactivity contains extensions to the Blend SDK
• PopupWindowAction class added to allow a custom window to display in response to interaction request being raised.
• The InvokeCommandAction provided by Prism now passes trigger parameter's to the associated command. This was a community request on CodePlex.

Code Samples

We created the Interactivity QuickStart in this release to demonstrate how views and view models can interact with the user. This includes interactions triggered from the view model and interactions fired by controls located in the view.

We also migrated the Silverlight QuickStarts to WPF:

• Basic MVVM
• State-Based Navigation
• View-Switching Navigation
• UI  Composition

CodePlex Issues Resolved

• 8532: InteractionRequestTrigger can cause memory leaks with some implementations.
• 9153: 'Notification' really should be an interface.
• 9438: Navigation to an existing view.
• 5495: Event to Command.
• 8101: DelegateCommand is not extendable.
• 5623: Make WeakEventHandlerManager public.
• 9906: A bug when using XAML module catalog in WPF.
• 7215: Issue with ModuleCatalog.CreateFromXaml for WPF application with MEF Bootstrapper.
• 8703: RegionManager::IsInDesignMode.
• 4349: Default Region Behavior Order Problem.
• 3552: Region manager in V2 fails to recognize non-WPF applications.

Where to Get It?

Documentation

• Online Documentation: https://aka.ms/prism-wpf-doc
• PDF: https://aka.ms/prism-wpf-pdf
• Online API Reference Documentation: https://aka.ms/prism-wpf-prism50refdoc
• API Reference CHM: https://aka.ms/prism-wpf-prism50refdocchm

Source Code

• Source Code including library and all samples: https://aka.ms/prism-wpf-code
• Samples
• Stock Trader Reference Implementation: https://aka.ms/prism-wpf-RICode
• Hello World: https://aka.ms/prism-wpf-QSHelloWorldCode
• Modularity with Unity: https://aka.ms/prism-wpf-QSModularityUnityCode
• Modularity with MEF: https://aka.ms/prism-wpf-QSModularityMEFCode
• Interactivity: https://aka.ms/prism-wpf-QSInteractivityCode
• MVVM: https://aka.ms/prism-wpf-QSMvvmCode
• Commanding: https://aka.ms/prism-wpf-QSCommandingCode
• UI Composition:  https://aka.ms/prism-wpf-QSUIcompositionCode
• State-Based Navigation: https://aka.ms/prism-wpf-QSStateBasedNavCode
• View-Switching Navigation: https://aka.ms/prism-wpf-QSViewSwitchNavCode
• Event Aggregation: https://aka.ms/prism-wpf-QSEACode

Binaries

• NuGet Packages: https://aka.ms/prism-wpf-nuget

Where to Start?

Where to start depends on your goals and what you already know.

Learn: If you are new to Prism, this is a good place to start.

• Learn about Prism Capabilities: Introduction.
• See how to consume the Prism Library in using the code samples.
• Learn the Prism concepts.
• Where to ask questions?

Develop and Deploy Applications: If you want to create a Prism Hello World application and deploy it then go through these topics. If you want to more fully understand how to utilize specific Prism capabilities in your application then read the Prism Landing Page.

• How to get your machine ready.
• Where to get library binaries.
• Create your first composite Prism application: Getting Started Using the Prism Library Hands-on Lab.
• Deploy Prism App: Publishing and Updating Applications Using the Prism Library Hands-on Lab.

Upgrade from Prism 4.1: Read the topics below so you can perform a cost benefit analysis of upgrading to Prism 5.0.

• What's New in Prism 5.0.
• Upgrading from Prism 4.1.

What about .NET 4.0, Silverlight, or Windows Phone 7

If you are developing for .NET 4.0, Silverlight, or Windows Phone 7, you should continue using Prism 4.1.

Documentation

• Online Documentation:
• API Reference Documentation
• Desktop
• Silverlight
• Windows Phone 7
• Offline Documentation: contains PDF and CHM

Code

• Source Code
• NuGet Packages

What happened to Prism 4.2?

We decided to change the version to 5.0 because there are breaking changes with this release. The breaking changes include:

• Reference changes – Prism reference changes to Prism.Composition, Prism.Interactivity, Prism.Mvvm, and Prism.PubSubEvents
• Removal of Silverlight

What’s Next?

Windows Phone 8.1 and Windows Store 8.1

We will create a version of Prism that  allows you to reuse code from apps that run on Windows Phone 8.1 and Windows Store 8.1. We will start with the Prism.StoreApps, Prism.PubSubEvents, and Prism.Mvvm projects and use the Universal project with the new version of Visual Studio. We will provide updates as we go. These are often referred to as Universal or Convergent Apps. The first drop is available on CodePlex.

Prism Apps for WPF and Windows Runtime

We are considering creating guidance on how to take your Prism for WPF and/or Silverlight applications and create Companion Apps on Windows Phone and Windows Store. I’ve had a number of developers ask if there is a way to preserve your investment in creating Prism apps that use modules and regions on the Windows Runtime. This is an area we are considering exploring.

The other request I’ve heard from a number of you is how to use modular development for apps that run on Windows Runtime.

If you have other suggestions please let me know.

This project was just released. See the blog post announcement.

Scope

Prism library updates

The major theme for the release is to move classes to Portable Class Library (PCL) and to address some of the requested CodePlex issues. In Prism for the Windows Runtime we moved the Event Aggregator to PCL. For this release we will move classes that support MVVM to PCL. For the classes that are moved to PCL, we will make the WPF versions obsolete.

Going forward you will see us put as much into PCL as is appropriate and reasonable.

Here is what we are doing for Prism in this release:

• ViewModel Locator: migrate ViewModelLocator from Prism for Windows Runtime to be a Portable Class Library and use it in Prism for WPF.
• BindableBase: migrate BindableBase from Prism for Windows Runtime to a Portable Class Library and use it in Prism for WPF. There is a request to add CallerMemberName to NotificationObject. We decided to port BindableBase from Prism for Windows Runtime to PCL as it already supports CallerMemberName. This means we will make NotificationObject obsolete in this version.
• Navigation: allow a dev to pass an object as a navigation parameter. This is a CodePlex request.
• InteractionRequest: migrate InteractionRequest to WPF. This is a CodePlex request.
• DelegateCommand: migrate DelegateCommand to a Portable Class Library. In a future release, Prism for the Windows Runtime will use the PCL version of the DelegateCommand.

Quickstarts

• Basic MVVM Quickstart.
• Create WPF version.
• Add ViewModel locator.
• Demonstrate how to construct parent-child Views and ViewModels.
• Demonstrate how to communicate between parent and child.
• State-based Navigation Quickstart.
• Create WPF version.
• UI Composition Quickstart.
• Create WPF version
• View-Switching Navigation
• Create WPF version

Drops & Release

Francis Cheung posted a drop today to CodePlex. Once we complete the release we will create NuGet packages and publish the source code on the Microsoft download center.

In this Drop

• Prism
• ViewModel Locator and Bindable Base ported to PCL
• NotificationObject is marked obsolete
• Interaction Request working for WPF
• Using .NET 4.5.1 and latest version of Unity and the Common Service Locator
• Navigation passes an object and a string
• ErrorsContainer, NotificationObject, CompositePresentionEvent marked as obsolete.

• Basic MVVM QuickStart using Prism ViewModel Locator.
• The ViewModel Locator uses a convention based approach to wire views and view models. In our XAML we tell the ViewModelLocator to AutoWire the view and the view model.

prism:ViewModelLocator.AutoWireViewModel="true"

• The convention assumes:
• View models are in the same assembly as the view types
• View models are in a .ViewModels child namespace
• Views are in a .Views child namespace,
• View model names correspond with view names and end with "ViewModel".
• For more information on how the ViewModel Locator works see the Prism for Windows Runtime documentation. We will provide documentation on how to modify the default convention.

• Prism, Stock Trader reference implementation, and Quickstarts updated to use BindableBase (Prism.Core) and PubSubEvent (Prism.PubSubEvents).

• CodePlex requests resolved
• 10110 - Unity not compatible with UnityExtensions
• 9439 - Navigation to an existing view
• 8121 - Prism ContentControl Region RequestNavigate - View already exists in region
• 9439 - [MEF] Navigation to an existing View
• 9118 - Extract Core Application Functionality to Core Assembly (Prism.Core)
• 9107 - NuGet packaging

Check out the drop and let us know your thought.

This is an update from the version released in May for Windows 8.

The guidance demonstrates:

• How to implement pages, touch, navigation, settings, suspend/resume, search, tiles, and tile notifications.
• How to implement the Model-View-ViewModel (MVVM) pattern.
• How to validate user input for correctness.
• How to manage application data.
• How to test your app and tune its performance.

What’s new in the Windows 8.1 version

Documentation

• Created a developer task topic to help developers learn how to complete key Windows Store dev tasks for validation, creating pages, navigation, touch, tiles, search, performance, testing, deployment, extended splash screen, incremental loading, Model-View-ViewModel (MVVM),  loosely coupled communication, and using the Prism libraries.
• Added the AdventureWorks Shopper logical architecture to help you understand what code you need to write for a Windows Store app vs the code the Prism library provides.
• Updated PDF for Windows 8.1.
• Provided release notes on CodePlex including a change log and late breaking news.

AdventureWorks Shopper Reference Implementation

• Created AutoRotatingGridView grid control to create a fluid page layout that responds to user requests to change the pages size and orientation
• Demonstrated using the IncrementalUpdateBehavior Blend Behavior for large data to improve user perceived performance
• Cleaned up styles
• Used Flyout/MenuFlyout instead of popup
• Changed FlyoutViews to use SettingsFlyout
• Used out of the box control for Watermark
• Used Blend Behaviors
• Used SearchBox & new search APIs
• Updated top/bottom app bars to use CommandBars and Action Buttons
• Used Windows.Web.Http.HttpClient instead of System.Net.Http.HttpClient

Prism for Windows Runtime

• Updated VisualStateAwarePage to detect page size and orientation
• Removed FlyoutService and FlyoutView
• Removed SearchPaneService and SearchQueryArguments. Used new SearchBox control instead.
• Added support for an extended splashscreen

Quickstarts

• Created Incremental Loading Quickstart to demonstrate how to improve end user perceived performance for a large grid by handling the ContainerContentChanging event, or by using the IncrementalUpdateBehavior Blend Behavior vs traditional data binding.
• Created Extended Splash Screen Quickstart to demonstrate how to use the Prism library to create an extended splash screen.

Where to get it?

• Documentation on the Windows Development Center.
• PDF version of the documentation will be available later this month.
• Source code for AdventureWorks Shopper reference implementation and the Prism libraries.
• Source code for the associated quickstarts.
• Via NuGet – use NuGet package Manager in Visual Studio and search online for Prism.StoreApps and Prism.PubSubEvents

If you need the source code for the AdventureWorks Shopper reference implementation and the Prism library that runs on Windows 8 we moved it to our CodePlex site.

Where to start?

• Review the AdventureWorks reference implementation. After you download the code, see Getting started with Prism library for instructions on how to compile and run the reference implementation, as well as understand the Visual Studio solution structure.
• Review Quickstarts. The Quickstart samples focus on specific tasks such as validation, event aggregation, bootstrapping an MVVM app, and adding an extended splash screen to your app.
• Create an app. If you want to create your own app using Prism see Using Prism for the Windows Runtime.
• Explore developer tasks. Learn how the Prism team implemented many of the tasks required to create a Windows Store app.
• Review the documentation. The associated documentation outlines the key decisions and lessons learned to create a Windows Store business app.
• Review the release notes. The release notes provide late breaking updates and a more detailed log of the changes in this release.

What code do I write and what does Prism library provide?

We included the AdventureWorks logical architecture in the documentation to help you understand what code is provided by the Prism library and what code you will need to create for your Windows Store business app.

Community

Prism for the Windows Runtime has a  community site you can post questions, provide feedback, connect with other users to share ideas, and find additional content such as extensions and training material. Community members can also help Microsoft plan and test future releases of Prism for the Windows Runtime. For more info see patterns & practices: Prism for the Windows Runtime.

So go download the code and get started creating your Windows Store app with Prism. We want to hear about your successes and challenges on our CodePlex site. What else do we need to add to the library and associated documentation? Many of the additions to this release came from user feedback from the CodePlex site.

Scope for Windows 8.1

AdventureWorks Shopper Reference Implementation Changes

• Demonstrate large data for grid and list view
• Clean up styles
• Use Flyout/MenuFlyout instead of popup
• Change FlyoutViews to use SettingsFlyout
• Use out of the box control for Watermark
• Use Blend Behaviors
• Use SearchBox & new search APIs
• Update top/bottom app bars to use CommandBars and Action Buttons
• Use Windows.Web.Http instead of System.Net.Http

Update Prism for Windows Runtime

• Update VisualStateAwarePage to take advantage of new view states
• Remove FlyoutService and FlyoutView
• Update SearchPaneService and SearchQueryArguments to use new Search APIs
• Add support for an extended  splashscreen

Release Date

We plan to complete the code and publish the associated guidance to the Windows Dev Center in December.

In defining the scope for this release and the patterns & practices roadmap, we looked at the highest requested issues identified on CodePlex. This includes:

• **Portable library for Windows Store and Phone: p&p roadmap
• **Support logging: p&p roadmap
• Support custom dialogs
• *Target Windows 8.1: in this release
• Support complex objects as navigation parameters
• *Add Flyout Page Support: in this release
• Add new Hub Page
• *Add Behavior SDK:  in this release
• Protocol Activated and File activated –> NavigationServer == null
• FlyoutViewModel / FlyoutView base class

The items with an * are in this release.

The items with ** are on the patterns & practices roadmap.

Go check out the release announcement.

This drop includes:

• Using Windows.Web.Http.HttpClient instead of System.Net.Http.HttpClient in the client app.
• Using SettingsFlyout instead of Prism FlyoutView. Deprecated FlyoutView and FlyoutService.
• Updated VisualStateAwarePage to listen for page size change and change VisualState accordingly.
• Updated bottom app bars to use CommandBar and AppBarButtons
• Cleaned up unnecessary styles.
• Added spikes for ListView/GridView performance and AutoRotatingGridView.

Let us know your thoughts.

• Chinese Simplified
• Chinese Traditional
• English
• French
• German
• Italian
• Japanese
• Korean
• Portuguese
• Russian
• Spanish

How to get Prism for Windows Runtime

The Prism library source code is available with the AdventureWorks Shopper reference implementation on the MSDN Code Gallery at https://aka.ms/prism-winrt-code. The Prism binaries are available on NuGet. Search for Prism.StoreApps and Prism.PubSubEvents. You need to NuGet Package Manger 2.1 or higher.

You can download a PDF version at https://aka.ms/prism-winrt-pdf.