The last month or so, I've been wallowing in Windows Presentation Foundation (WPF), trying to determine if it is the correct direction for our next version of our flagship software, ParaPlan. WPF is flashy and fun and bubbly, but there are not many examples of real world enterprise applications that are built around WPF. After much research, and significantly pushing back our deployment timeline, we decided to rebuild ParaPlan 4.0 using WPF for our UI.
We were able to use our existing 2.0 UI framework and use ElementHost for new development in WPF, but didn't want to chance a performance or scalability hit with the interop components. My WPF code that lived in ElementHost inside a proper UI framework with visual and functional inheritance seemed fragile at best.
This series of posts that will describe my daily battles with WPF will hopefully serve as a reference point for architects considering moving to a WPF framework. My first couple of posts will talk about the deal breakers that our application needed.
Technorati tags:
WPF,
EnGraph,
ParaPlan