Question

It seems that the only way to really evaluate a UI control suite is to download the trial and invest many hours in understanding its limitations and design flaws. However, with so many to choose from, I am trying to shorten this process by ruling out those that fail to meet a key criterion – MVVM compatibility.

What are your experiences in deploying the various suites in projects that use MVVM and which, if any, are specifically designed with MVVM in mind?

Answer 1

I mostly agree with Dan; As he mentioned controls should have built in capability to fire a Command, at the same time control properties should be dependency properties so as to use binding with them(I have faced this issue with some of the 3’rd party controls).

I have evaluated Telerik, Infragistics and Syncfusion controls for my projects and have extensively used Telerik and Syncfusion.

From my experience I feel Telerik are best designed controls and best suited for MVVM. I have seen telerik’s code as well and they themselves use MVVM pattern.

I haven’t used Infragistics extensively so can’t comment whether they suit for MVVM or not but they have good and stable controls.

Syncfusion is worst when it comes to WPF, there controls are not that great and will be tough to use with MVVM. They are neither well designed nor very stable.

One tip to check this compatibilty –

check(glance through) the samples for these controls. If they have used MVVM in there samples or have used Commands, Binding etc. extensively in there samples, then they will be more suitable to be used with MVVM.

As far as I remember, I have seen MVVM in Telerik’s control, where as Syncfusion samples don’t use most of the features of WPF in there samples, they look plain WinForms samples used in WPF application.