Prism 5.0 for .NET 4.5

Rating:        Based on 41 ratings
Reviewed:  25 reviews
Downloads: 0
Released: Jan 14, 2014
Updated: Apr 19, 2014 by blainew
Dev status: Stable Help Icon

Available Downloads

There are no downloads associated with this release.

Release Notes

Download Prism 5.0 for .NET 4.5.1 at

Reviews for this release

by lufengwen on Sep 25, 2017 at 3:46 PM
it's good.
by LiHu4321 on Aug 7, 2017 at 2:38 AM
by Fuad1907 on Jul 2, 2017 at 8:48 AM
very good ,this is wonderful
by linjiewang on Mar 20, 2017 at 5:35 PM
Real Useful
by ShowMustGoOn on Jan 12, 2017 at 5:31 AM
very goood
by cd200607139 on Jan 3, 2017 at 10:06 AM
thank you very much!!
by zixubingfeng on Nov 11, 2016 at 6:19 AM
good work!
by jiangjian on Apr 8, 2016 at 4:14 AM
It is super effective.
by smdhz on Apr 10, 2015 at 3:16 AM
I need it!
by brucezhang80 on Mar 23, 2015 at 5:20 PM
a good framework
by rennai0218 on Mar 10, 2015 at 7:32 AM
by suntanyong88 on Dec 11, 2014 at 10:27 AM
A good framework
by codemarine on Aug 4, 2014 at 7:25 AM
a very wonderful tool for us to use mvvm
by wangyanxin on Jul 26, 2014 at 2:57 AM
不知道是什么东西哦 拿下来看下
by ssp on Jun 16, 2014 at 7:11 PM
Prism Team, After looking at Prism 5.0 I'm altering my original comments and rating. I still don't understand the reason for breaking Prism Desktop in multiple assemblies, but users can reorganize and rebuild the Prism Library if desired. As I said before, I would recommend publishing WPF Desktop Guidance separate from WinRT Guidance. Not sure if this is why some classes were broken out or not. I recommend single platform targeting because it makes Enterprise application maintenance simpler in the long run. When you mix platforms, you have to make concessions to get it to work, ultimately the product is not as good as it could be. Think back to Prism 4 and Silverlight and WPF. Design decisions were made to support Silverlight, but API's could be cleaner and simpler when not trying to target multiple platforms. I really like the new generic pub-sub implementation, nice work on this. Respectfully, Karl Shifflett - Long time Prism Enterprise Developer
by molenator on May 22, 2014 at 1:05 AM
Karl can you list the breaking changes so we can see if there is a way to eliminate them? As an fyi, the ViewModel locator is only used in 1 quickstart. The Stock Trader RI wires views & view models the way it did in Prism 4.0.
Reply by blainew (N/A) on Jan 20, 2014 at 6:14 PM
No Silverlight support = No PRISM... From mine point of view of course... :-( BB
by krzemo on Apr 28, 2014 at 9:30 AM
Good work! But, Why don't add wpa8.1 from nuget target framework? I hope wpa8.1 support.
by okazuki on Apr 21, 2014 at 2:48 AM
Good asdfasdf asdfa sdfsdf
by DenisX on Apr 13, 2014 at 1:22 PM
I tried to download this beta and compile the Prism library on Windows 7 with Visual Studio Express for Desktop, but the Prism.Mvvm and Prism.SharedInterfaces was reported as not compatible types.
by rinojohnsen on Mar 20, 2014 at 1:47 PM
I'll update my software to prism 4.2 When will the stable version release?
by chenyaojun on Mar 20, 2014 at 2:13 AM
There is no valid nuget package in main repository. Also must totally agree with molenator: too many breaking changes for enterprise.
by BlackGad on Mar 17, 2014 at 11:57 AM
I've begun using this version of PRISM for new software projects. I think that it is fantastic that the team working on this is continuing to revise and integrate the new features available in .NET 4.5.1. The team I'm part of all have VS2013, and I'll continue to recommend PRISM for future development of software. While some of the changes are departures from how things were done previously, I think it is fantastic to see support for the newer, exciting features available in .NET 4.5.1.
by SpencerP on Jan 30, 2014 at 6:19 AM
I downloaded the sample but NONE of the quick starts work. It seems like the Service Locator was not included in the download.
by DDority on Mar 3, 2014 at 10:19 PM
You need to compile the Prism library first and then you can compile and run the quickstarts. Once we publish NuGet packages for the library we will change the RI and QuickStarts to take NuGet references and this issue will go away. I hope this helps. blaine
Reply by blainew (N/A) on Mar 4, 2014 at 12:24 AM
I used prism for Silverlight 5 development. Dropping support for it is unacceptable.
by ShawnExplore on Feb 10, 2014 at 8:30 PM