>> 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.