For seven years since the Prism project started, led by the patterns & practices team, was originally known as the Composite Application Library. Last year was the 5th official release of Prism. The two major focuses of that release were: compos ability and ease of community contribution.
From the beginning, Prism has had a strong community focus. This hasn’t simply been a matter of surveys and user studies, but frequent discussions and regular code reviews with community members and industry experts. Now it’s time to take Prism to the next level.
Ownership of Prism projects is transferred to community members.
- Brian Lagunas. Brian is a Microsoft MVP whose involvement in the project started with Prism 2. .
- Ariel Ben Horesh. Ariel has been involved with Prism since its first release.
- Brian Noyes. Brian is also a Microsoft MVP and has also been involved with Prism since its inception.
There is a strong continuity for the project since the new owners have been significant contributors since the beginning. As part of this hand-off, the projects will be consolidated in the PrismLibrary org on GitHub. Likewise, discussions are underway about bringing Prism into the .NET Foundation. This change of ownership means that future releases of Prism will be developed by the new team, not by Microsoft.
The Prism team’s plans on their Roadmap
The idea is to improve an already mature product with new features and to support new platforms (can you say Windows 10?). Already have a number of items that we will be addressing in the next version of Prism. Here is a highlight of some of them.
- Remove the dependency of Prism.PubSubEvents from Prism.Composition
- Remove all deprecated classes and properties
- Fix that annoying namespace bug with Prism.Mvvm
- Fix that annoying bug with the ViewModelLocator design time exception. (We will remove the need of IView altogether)
- Add CallermemberName attribute to BindableBase.OnPropertyChanged
Besides these small feature improvements, we will also be looking at restructuring the Prism solution to make a more cohesive product, reduce dependencies, and to better support cross platform development; such as iOS and Android using Xamarin.Forms. You can expect a number of breaking changes in the Prism 6 release as we take Prism in this new direction.
. We’re excited about Prism’s future.