taspeotis wrote:Hi all,
I've got my eye on Prism/WPF because the company I'm at is currently evaluating frameworks to replace or augment our C++/MFC-based one.
One criteria for evaluating frameworks is longevity, which stems from our existing MFC codebase. If MFC was under development which would see improvements to the core library and the designer tools I think we'd be less likely to look for MFC replacements.
My concern is that the p&p roadmap doesn't seem to offer any guidance on Prism/WPF on the desktop; the roadmap seems to be focusing on WinRT (but that's not to say that a framework that runs on the desktop is mutually exclusive from a framework that runs on Windows Store.)
I'm wondering if anybody can point me towards some guidance that suggests Prism/WPF will continue to see development for desktop applications? The MFC code in the application I work on is up to 20 years old and the next windowing framework we pick might have to go another 20 years before we change it again.
If there is none or no further consideration for Prism on the desktop besides v4.5 please consider this post a +1 vote for p&p to continue to work on desktop technologies.
Are there things about building desktop applications that you feel Prism does not address adequately today? Prism does not try to be all things to all people, but it remains the p&p guidance for building loosely coupled, testable, maintainable, small to large
scale desktop applications for Windows (XP -> 8 and beyond).
Brian