why not a proper release some thing like PRISM 2.2 for VS 2010?

Topics: Prism v2 - WPF 3.5
Apr 29, 2010 at 3:14 AM

As VS 2010 is available , Enterprise library 5 is here. PRISM 4.0 is not coming very soon. What if you people release some thing like PRISM 2.2 or 3.0 rather than builds. I am reading some where that these builds are not fully tested. What you say to those developers which are starting a new project with VS 2010 and enterprise library 5 should they use builts.

Apr 29, 2010 at 6:24 PM
Edited Apr 29, 2010 at 6:24 PM


There is probably going to be an interim updated, most likely called Prism 2.2, as stated on this blog post by the Patterns & Practices Client Team. As mentioned in this blog post, no issues have been reported with this new build, but it was only smoke tested.

I hope you find this helpful.

Guido Leandro Maliandi

May 10, 2010 at 9:05 PM

Hi Guido,

I could see the WPF composite dlls are built on .NET 3.5, not on .NET 4.0 as mentioned in the blog post:



Do you have plans to release an updated version with .NET 4.0 projs? Any reason why they are still .NET 3.5?




May 11, 2010 at 12:36 PM

>>  Any reason why they are still .NET 3.5?

There are a bunch of us in the corporate environments that dont have the ability to move to 4.0 yet.  There are lots and lots of restrictions on what software is allowed and to use it, it has to go through the proper governance procedures. 

Its a pain, but a normal part of life in big corporations.  We dont always get to move with the rest of the world.  Heck, I am writing this on XP sp3, not by my choice, but because that is the corporate standard until Win 7 gets approved and moved to the desktops.  Vista was a no go.  Win 7 is early next year at the soonest, maybe.  .Net 4.0 might make it by the end of the year.  Certain groups might get exceptions and be able to run those earlier, but only on a limited set of client desktops as "proving ground".

When you have 10's of thousands of desktops, its a big thing to approve both OS's and the software that runs on them. 

It is my impression that the Corp world is a large target market for Prism.  If the current distribution went to 4.0 and vs2010 exclusively, it would alienate a large percentage of that market IMO. 

I agree though, that the current prism should be able to be built and available in both 3.5 and 4.0 versions, and that there shold be a release that does just that.  

IMO, Prism vNext should target 4.0, but it should maintain backward compatibility if at all possible.  If it cant, at least keep the 3.5 version working and quasi supported until .net 5.0 and vs2015 hits the streets.  Create a branch, or whatever is needed, but dont drop the current prism's 3.5 compatibility/buildability for a while.  Please. 

In my personal environments, I love to see Prism vNext use the latest and greatest.  But the work environment aint quite the same.


May 11, 2010 at 1:31 PM

Totally agree with pmon.  We are still on XP SP3 at my large corporate environment and while we have been able to get SL3 and .NET 3.5 passed it is unlikely that we will get to move to SL4 and .NET 4 for quite a while.  Very frustrating for us I can tell you!!  

I wouldn't want to hold people on the bleeding edge back but we also want to have some decent roadmap for our continued use of Prism.

May 11, 2010 at 1:57 PM

Also at big corp.  Just to offer a different perspective.  Unless software is released, it doesn't get approved for use.  Delaying a version for 4.0 Framework doesn't help anyone.  In our case, we are working on a brand new 'big corp' software package for the enterprise.  We were able to get it approved for VS2010 and 4.0 Framework because it will take over a year to get into production.  The further we get along in development, the harder it will be to upgrade anything.  But I can tell you that at the moment, we are using VS 2010, .NET 4.0 and the latest PRISM/CAL/CAG (Whatever you call it!).  It all compiles and runs fine without complaint.

May 13, 2010 at 12:18 AM

We are working on a Prism 2.2 that will be dropped to Codeplex. This version will target VS2010 and .NET 3.5. The point of this version is to provide a version of Prism that works with Silverlight 4. If anyone needs VS2008 and .NET 3.5, the current version on MSDN will work.

Blaine Wastell