Prism 6 for UWP, Prism 6 for WPF update + a new logo to adorn its new home

Back in the spring we announced that the Prism framework had gone open source and that Brian Lagunas and myself would be the primary owners of the framework moving forward. We also joined the .NET Foundation, and they have been awesome at helping us quickly mature into a fully functioning open source project team. Now we have an official logo for the project that you will see us using moving forward on the project. Behold!


We have been working hard on getting an initial release out since turning full OSS, which we are calling Prism 6. Things had fragmented a bit with Prism in recent years with Prism 5 being the most recent release for WPF, and Prism for Windows Runtime having what they called a 2.0 release that targeted Windows 8.1 and Windows Phone 8.1 Universal apps. Well the world keeps on moving and now we have Windows 10 UWP to target as well, and Xamarin Forms has been quickly gaining momentum in the mobile space.

We’ve had some great engagement from the community in the form of jumping in and helping us make decisions on what way to go with issues being raised with the code base, new feature suggestions, and pull requests to help get us there. I want to especially call out Bart Lannoeye who has jumped in as an advisor and has been contributing a ton to managing the project, submitting pull requests, helping us get our NuGet story together and lots of other stuff… in reality he has been working a lot more on Prism than me lately, so thanks for that Bart!

So the focus lately has been:

  1. Get Prism 6 for WPF out the door, which happened about a month ago. We just pushed out a new release today (6.1). NuGets should be live within a day or so, Brian Lagunas is working on automating our process for generating those since we have a lot of them now due to targeting three platforms and 5 different DI containers. We’ve still got a lot of new things planned, but this is a good stable release that people can feel confident moving to from Prism 5 if they want to be able to move along with us as we release incremental changes. Because of the change of ownership, that did mean we changed namespaces, and also based on our focus moving forward of targeting WPF, Windows 10 UWP, and Xamarin Forms there was some moving things around into a new assembly structure. But those changes are all quick and easy to patch up when you move to Prism 6 by removing the old NuGet packages for Prism 5, add the new ones for Prism 6, and do some find and replace on namespaces to get everything good to go. Our release notes here tell you what the breaking changes were in this release.

  2. Get an initial release of Prism 6 for UWP out the door. The starting point for this was to migrate the code base of Prism for Windows Runtime to UWP. Most things came over pretty cleanly, but there are a lot of things different there as well. That is out now and available on NuGet.

  3. Build up a new Prism 6 for Xamarin Forms library. Brian Lagunas has been leading this effort and has the code out there as a prerelease that you can start using today, but we are still a little ways out on getting a first release of that out. There are some changes coming in an update from Xamarin that affect Prism, so we are holding off until that update comes out.

So if you are a previous user of Prism, or are just brand new to it, check it out! We have a lot to offer to help you structure your XAML apps for long term maintainability and extensibility using patterns including MVVM, Dependency Injection, modularity, UI composition and so on. And if you want to get involved helping us evolve it, get engaged with us through our Github repo