Winforms vs WPF
Posted by - NA - on 06 September 2010 12:53 PM
Since among our products we've offered our users a new RadarCube version for WPF, they've been asking us if this means we're no longer going to develop the WinForms version and what version should they choose - WinForms or WPF?
The answer is this: no, we won't stop developing the WinForms version - all the versions will be developed as simultaneously as possible.
As for selecting between WinForms and WPF - a number of factors should be taken into account before you make the choice.
First, the WPF version is relatively "green", thus it doesn't have some interface solutions implemented in the WinForms version. The most important of them are conditional formatting and export procedures.
Naturally, these are merely temporary inconveniences. Right now the development of the WFP version goes far ahead of WinForms, due to our desire to "equalize" the facilities of both versions.
On the other hand, compared to WinForms, WPF is a more advanced platform, thus it already has a few implemented mechanisms that most likely will never appear in WinForms. That's - first of all - is the option of placing arbitrary content in a Grid cell (i.e. arbitrary WPF content) and paging hierarchy members, same as in the ASP.NET versions.
By the way, due to the implementation of the paging mechanism (that, of course, can be disabled, if necessary) the performance of the WPF-version is much faster than that of WinForms.
In conclusion, a few words about the compatibility issue: the WinForms version operates under the NET Framework 2.0 platform and requires Visual Studio 2005 and above as its development environment. WPF's requirements are way more serious. The minimal requirements are: NET Framework 4 and Visual Studio 2010.
So, as always: the choice is yours and we'll do everything so that our products will meet your expectations!