The (no) future of Prism for Windows Runtime

Apr 15, 2015 at 9:18 AM
It seems that there are good and bad news.
The good news: Prism is alive and will now be developed by Brian Lagunas, Brian Noyes and Ariel Ben-Horesh. (Blaine, and you? Where are you?)
The bad news: Prism for Windows Runtime is legacy. There will be no updates anymore.
Instead of Prism for Windows Runtime a new version for Win 10 will be developed.
Concrete plans will be available after the Microsoft Build even.
Read more on the blog of Brian Lagunas
Apr 15, 2015 at 12:31 PM
That is not true, you are reading too much into that post. We have no intentions of releasing a new version of Prism for Windows Runtime targeting Windows 8/8.1 only unless people submit issues to our repo ( that warrant attention. And if they do, we encourage the community to pitch in and help develop those new features. And what we expect to do post Build will be an evolution of Prism for Windows Runtime and will hopefully be backward compatible for Windows 8 apps. We will have to see when we build that backlog.

But we definitely encourage people to submit issues or feature requests against the Prism for Windows Runtime code base to help guide what we decide to do there. Prism for Windows Runtime is definitely not dead either. We are just not immediately focusing on it because we want whatever we do with it to be guided by where Windows Runtime is going under Windows 10. Windows 10 is still a WinRT-based programming model, so it should be an evolution of the current universal apps code. But one intention we already have even if we don't add any new features is to clean up that code base - the 2.0 release seems to have been put together in a bit of a hurry by the p&p team and is a little confusion on the organization (i.e. three different versions of the .StoreApps library in there) - so at a minimum we will be doing some clean up there.

If you have specific issues or things you would like to see done with it, please submit issues against our GitHub repo.
Brian Noyes
Apr 16, 2015 at 1:33 PM
Edited Apr 16, 2015 at 1:37 PM
I am a bit confused, then!
If someone wants to start now (working with the Windows 10 preview and Visual Studio 2015 CTP) to develop a new universal app for the next 10 platform, there is already a version of Prism that he can use for implementing the MVVM pattern? If not, when it will be available and where?
Other MVVM frameworks are already supporting WIN 10 developments (e.g. ) : what about Prism?

Thank you
Apr 16, 2015 at 1:53 PM
The current Prism for Windows Runtime bits should work fine for basic MVVM for Win10 Preview. We plan to do a pass on that and make any updates in our new repo at needed in the next couple weeks leading up to Build. Once the full development story for Win10 is unveiled at the Build conference, we will figure out what other changes need to be made to bring it into alignment with the Win10 platform and possibly bring some of the features over from the WPF version that were intentionally left out of the initial Prism for Windows Runtime releases (i.e. modularity and regions).

Please start moving conversations regarding Prism future over to the discussion boards at our github repo, since that is where all future work on Prism will be conducted.
Apr 16, 2015 at 2:46 PM
Thank you Brian for your prompt reply!

If I took it well, there will be, in the next few weeks, a new repository in (different from the actual Prism.MVVM one) specific for providing a MVVM pattern support for universal Windows/WP 10 apps. In the meanwhile you suggest to start using this codeplex version, event thought (see ) it seems to be issues at least related to the SettingPane handling: can you provide some further suggestions?

Related to start moving conversations regarding Prism future in GitHub, I couldn't find any discussion board (like this forum in codeplex project) where someone can ask/answer questions: surely I am wrong so could you possibly provide the link of the discussion boards who talk about in your previous post? Thank you.

Apr 16, 2015 at 2:53 PM
It will be under the \Prism repo. We already have the current 8.1 code there.

Don't have any specific comments on problems at this point because I haven't had time to look into it.

For discussions I meant if there are specific issues you want addressed, use the issues section. For general Q&A, stackoverflow is probably a better place for that kind of stuff anyway.
Aug 14, 2015 at 1:34 AM
I'm using Prism.StoreApps (and Unity) in a UWP project. That's going fine. However, I can't for the life of me get a UWP unit test project to work. Any guidance for how to achieve unit tests using Prism + Unity?


Aug 14, 2015 at 8:23 PM
I've already done an initial port of the Prism for Windows Runtime code to Prism for UWP. That code lives here now: I'll be working on it some more next week, adding in the validation code that I did not migrate yet and trying to address some of the other issues and pull requests we have received. In that initial migration I did bring across all the unit tests from Prism for WinRT, so you can take a look at those and maybe it will shed some light on what you might be having problems with.