We had to make a quite similiar decision a few months ago. We were using WinForms, the Microsoft Composite UI Application Block and DevExpress WinForms. For our new application, created new from scratch, we decided to use WPF (without PRISM) and we were especially in need of some grids, so we used DevExpress WPF Controls.
This was imho a good and a bad decision.
The good part:
You can use the controls in a very similiar way you are used to. There are some differences, but you get used to them quickly. This is a huge plus, because it took us quite some time to get used to them while using the WinForm controls.
The controls, especially the grids, are useable as the WinForms controls. If your users are used to them, the transition is very smooth.
Applying one of the provided themes is very simple and you get a good looking solution without much annoyance. They apply to pure WPF controls, too, so the whole application looks consistent. We are still using mostly Windows XP, the themes apply to this as well, which is exceptional useful for us.
The bad part:
We expected the DevExpress WPF controls to provide the same control coverage as the WinForm controls did. The DevExpress WPF controls at that time had version number 10.1, and we were disappointed that some controls were missing completely (for example TreeList, Schedulers, Passwordbox or the very useful LookUpEdit). While the later three are available with version 10.2, TreeLists still aren't there. If you are looking for additional controls from the WinForms package than the ones listed, it is a good idea to check if they exist for the DX WPF controls first.
Some parts made the impression that they were done quickly. There were some quickfixes neccessary to get the controls running the way we intended to use them. The good thing is that most of these problems are solved with 10.2.
The documentation and the support center for the WPF controls feels less complete than the WinForms documentation. While this is probably just my personal impression, I was almost always able to find an answer to a certain problem I had with the WinForms controls on the DX website, I'm not that succesful with the WPF controls. The support team is as helpful as always, though.
This list is not intended to be exhaustive, those were the things that immediately came to my mind.
So, what would I do if I had to do the same decision again? I would very likely use DevExpress again. Most negative things that bugged me were fixed with version 10.2, so the controls are quite usable now. I especially like that you can use your former experience with the WinForm controls (with limitations, of course). The later was also the primary reason for buying the DX components. Unfortunately, I don't know the Telerik controls enough to say anything about them, so if someone has experience with both, especially with switching from DX to Telerik that would surely be a very interesting information.
We're not using the MVVM pattern with our grids, as the "traditional" way of loading and displying data is sufficient enough for us. Some of our grids contain 100k+ values, the performance of the grid is imho always ok. The controls disn't look like they had a build in support for MVVM, if you're trying to use it it looks like you have to do everything manually. Maybe 10.2 changed things here, I haven't checked, but I don't think so.
We used our own implementation for localisation, so I don't know about the DX localization support.
Telerik 使用实体框架与 Sql Server 完美集成。它的分页、排序、过滤等功能直接与EF集成，并让Sql Server在数据库中完成这些操作。很不错！我在执行操作时监控了sql命令。如果您正在 sql server 上查看大量数据，这可能是真正能很好地做到这一点的一个控件。 （下拉过滤器组合除外，它不能很好地处理大数据）。我们使用 Mongo 来处理大数据，所以这不适用于我们。在测试数据时，Telerik 确实有一些例外。 DevExpress 没有分页选项，除非您自己设置。
最终我们选择了DV，因为数据量大且稳定的性能原因。
I evaluated several WPF control packages, Telerik, devExpress, Xceed, SyncFusion, etc. We were primarily interested in a grid control that could handle a large amount of data and have good performance. In a simple test, we loaded 120,000 items into the grid and did a group on the fields.
DevExpress was the fasting loading compared to the others. It took 15 secs to load, while the others where all about 45 seconds. DV would group in 7 seconds, while the others took nearly 45 seconds. A couple of the other controls packages locked up! (fyi, the data was being loaded from Mongo).
When bringing up the filter dialog for a column on Telerik, it would extend beyond the bottom of the screen without any scrollbar. Also, cicking on a filter item in the dropdown combo would immediately do the filter then rather than waiting for me to select the others. Therefore, if selecting 5 items, it would take 5 times as long.
I wish DevExpress would have a checkbox dropdown filter option (like Excel). You can only select a single value, but it does have a very nice filter dialog that allows you to do more complex filters. Still, would like to be able to easily check a few values and move on quickly.
Telerik integrated nicely with Sql Server using Entity Framework. It's paging, sorting, filtering, etc. integrated directly with EF and had Sql Server do these operations at the database. Very nice! I monitored the sql commands as doing operations. It you are viewing large amounts of data on sql server, this may be the one control that really does this well. (Except for the dropdown filter combo that does not handle large data very well). We are using Mongo for our large data, so this did not apply to us. We did have a few exceptions with Telerik when testing data. DevExpress does not have a paging option unless you it yourself.
In the end we chose DV due to performance reasons with large data and stability.
我肯定会选择 DevExpress，在我看来，他们的组件比 Telerik 的组件更好，并且具有更好的 API，那么我们不要忘记，您已经了解了 Windows 窗体世界中的对象模型、命名约定和 API，这不是一个小问题因为你很可能会重用你的专业知识，这更加重要和有价值。
I would definitely go for DevExpress, their components are in my opinion nicer and with better APIs than Telerik ones, then let's don't forget you already know their object model, naming conventions and APIs from the windows forms world, this is not a minor thing because you will most likely reuse your know-how and this is far more important and valuable.
The Telerik RadDataGrid supports MVVM and the command pattern properly straight out of the box. The DevExpress one requires a lot of extra code before you can use MVVM with it properly.
DevExpress WPF is slow and not optimized performance wise. I've tried rich text edit control of both DevExpress and Telerik. Telerik control outperforms DevExpress in terms of performance.
我同时使用 Telerik 和 DEVExpress。根据我的经验，DevExpress在win表单控件方面更好。但是，Telerik 比 Asp.NET 控件更好。 DevExpress 在服务器控件上的渲染结果在客户端站点上非常混乱。他们使用表标签创建按钮控件。
I am using Telerik and DEVExpress both. Based on my experience, DevExpress is better in win form controls. But, Telerik is more better than in Asp.NET controls. DevExpress rendering result on the server controls are very messy in client site. They create button control using the table tag.
I was exactly in the same position few months ago when evaluating WPF controls for a new WPF project. I’m not sure if you have made any decision, but I can offer my experiences with Telerik and hope it helps.
In my project, one particular need was to use TreeListView and there were limited reputed vendors provided this control. I spent some time doing researches and found Telerik which offered for what I needed. I downloaded the trial and used it for 2 months, contacted their support, checked their forums. I can tell you that they have excellent supports! Usually the supports provided solution with sample codes. Like all developers, we would encounter roadblock, we studied the API, documentations, and examples. For me, support is important as it saves development time! My feedback is Telerik provides great UI controls with vast collection and customization choices, and great technical supports. However, their documentation isn’t so good. Also, watch out performance in WPF controls, my experience is it has some performance hit if you have large data source. Be sure to do some prototypes in critical architectural areas if performance is the key requirements.
Just give it a try and see if it meets your needs or not.
BTW, I’m also ComponentOne customer. Just get the controls for what you need if it can save you time. The important thing is which helps ship your product on time! Hope this helps.
I'd take telerik hands down...#1 reason being support, #2 reason is that if the control can't do what you need you just need to put in a ticket or post to the support forums and you can DRIVE their feature development.
I believe devexpress is realy beter in WinFormApp. I'm using it for several years it's really nice. On the other hand recently I'h tried its WPF controls, It's terrible and full of bag I don't have time to switch to telerik for this project. Another problem that I had with devex is RTL. If You want to have a multi language app It can be important. Telerik can support RTL But Devex don't Support it in WinApp and in WPF in Devex don't supported it completely. AS I said devex is better in WinApp without RTL.
From my point of view DevExpress provides some what light weight controlls compare to Telerik. Reporting using DevExpress is more flexible. But at the same time Telerik having a better look and feel comapre to another tools.
I have a friend that uses Telerik controls and he absolutely swears by them. He specifically mentioned how their data grid control is the greatest thing since sliced bread and uses all the time (which might help you out based on your first bullet point).
Again, not firsthand experience, but I trust his opinions on these kind of things.
还没有尝试过 DevExpress，但我使用 Telerik for WPF 它有一些很好的组件，例如 Gridview。但其他组件充满了错误，例如一个简单的停靠控件，迄今为止他们还没有设法让它正常工作。
have not tried DevExpress, but I use Telerik for WPF it has some good components the Gridview for example. but other components are full of bugs example a simple dockcontrol to this day they have not managed to get it to work properly.
I used both telerik wpf radcontrols and the devexpress ! From my experience i was satisfied with telerik controls as my main objective was to be more productive and deliver a desktop application with a good UX in a short time ! Telerik make heavy use of the mvvm pattern and recommend using it as most of their demos are based on it ! As for documentation looking at the demos source code was enough for me to have a quick start ! On the other hand devexpress is more mature. in other words, telerik contains bugs but The support will always find a workaround for you if you ask.
发布评论
评论（13）
几个月前我们不得不做出一个非常相似的决定。我们使用 WinForms、Microsoft Composite UI Application Block 和 DevExpress WinForms。对于我们从头开始创建的新应用程序，我们决定使用 WPF（没有 PRISM），并且我们特别需要一些网格，因此我们使用了 DevExpress WPF Controls。
恕我直言，这是一个好的决定，也是一个坏的决定。
好的部分是：
您可以按照您习惯的非常相似的方式使用控件。虽然存在一些差异，但您很快就会习惯它们。这是一个巨大的优势，因为我们在使用 WinForm 控件时花了相当长的时间来适应它们。
这些控件，尤其是网格，可用作 WinForms 控件。如果您的用户习惯了它们，过渡会非常顺利。
应用提供的主题之一非常简单，您将获得一个美观的解决方案，而不会带来太多烦恼。它们也适用于纯 WPF 控件，因此整个应用程序看起来一致。我们仍然主要使用Windows XP，主题也适用于此，这对我们来说非常有用。
不好的部分：
我们期望 DevExpress WPF 控件提供与 WinForm 控件相同的控件覆盖范围。当时的 DevExpress WPF 控件的版本号为 10.1，我们对一些控件完全缺失感到失望（例如 TreeList、Schedulers、Passwordbox 或非常有用的 LookUpEdit）。虽然后三个在版本 10.2 中可用，但 TreeList 仍然不存在。如果您正在从 WinForms 包中寻找除列出的控件之外的其他控件，最好首先检查 DX WPF 控件是否存在这些控件。
有些部分给人的印象是它们很快就完成了。为了让控件按照我们想要使用的方式运行，需要进行一些快速修复。好消息是，这些问题中的大部分都在 10.2 中得到了解决。
WPF 控件的文档和支持中心感觉不如 WinForms 文档完整。虽然这可能只是我个人的印象，但我几乎总能在 DX 网站上找到使用 WinForms 控件遇到的某个问题的答案，但使用 WPF 控件却不太成功。不过，支持团队一如既往地提供帮助。
这份清单并不是详尽无遗的，这些是我立即想到的事情。
那么，如果我必须再次做出同样的决定，我会怎么做？我很可能会再次使用 DevExpress。大多数困扰我的负面问题在 10.2 版本中得到了修复，因此控件现在非常有用。我特别喜欢的是，您可以使用以前使用 WinForm 控件的经验（当然有限制）。后者也是购买 DX 组件的主要原因。不幸的是，我对 Telerik 控件的了解还不够多，无法对它们进行任何介绍，因此如果有人对这两种控件都有使用经验，尤其是从 DX 切换到 Telerik 的经验，那肯定会是一个非常有趣的信息。
我们没有在网格中使用 MVVM 模式，因为加载和显示数据的“传统”方式对我们来说已经足够了。我们的一些网格包含 100k+ 值，恕我直言，网格的性能总是好的。这些控件看起来并没有内置支持 MVVM，如果您尝试使用它，看起来您必须手动完成所有操作。也许10.2改变了这里的东西，我没有检查过，但我不这么认为。
我们使用自己的本地化实现，所以我不知道 DX 本地化支持。
We had to make a quite similiar decision a few months ago. We were using WinForms, the Microsoft Composite UI Application Block and DevExpress WinForms. For our new application, created new from scratch, we decided to use WPF (without PRISM) and we were especially in need of some grids, so we used DevExpress WPF Controls.
This was imho a good and a bad decision.
The good part:
You can use the controls in a very similiar way you are used to. There are some differences, but you get used to them quickly. This is a huge plus, because it took us quite some time to get used to them while using the WinForm controls.
The controls, especially the grids, are useable as the WinForms controls. If your users are used to them, the transition is very smooth.
Applying one of the provided themes is very simple and you get a good looking solution without much annoyance. They apply to pure WPF controls, too, so the whole application looks consistent. We are still using mostly Windows XP, the themes apply to this as well, which is exceptional useful for us.
The bad part:
We expected the DevExpress WPF controls to provide the same control coverage as the WinForm controls did. The DevExpress WPF controls at that time had version number 10.1, and we were disappointed that some controls were missing completely (for example TreeList, Schedulers, Passwordbox or the very useful LookUpEdit). While the later three are available with version 10.2, TreeLists still aren't there. If you are looking for additional controls from the WinForms package than the ones listed, it is a good idea to check if they exist for the DX WPF controls first.
Some parts made the impression that they were done quickly. There were some quickfixes neccessary to get the controls running the way we intended to use them. The good thing is that most of these problems are solved with 10.2.
The documentation and the support center for the WPF controls feels less complete than the WinForms documentation. While this is probably just my personal impression, I was almost always able to find an answer to a certain problem I had with the WinForms controls on the DX website, I'm not that succesful with the WPF controls. The support team is as helpful as always, though.
This list is not intended to be exhaustive, those were the things that immediately came to my mind.
So, what would I do if I had to do the same decision again? I would very likely use DevExpress again. Most negative things that bugged me were fixed with version 10.2, so the controls are quite usable now. I especially like that you can use your former experience with the WinForm controls (with limitations, of course). The later was also the primary reason for buying the DX components. Unfortunately, I don't know the Telerik controls enough to say anything about them, so if someone has experience with both, especially with switching from DX to Telerik that would surely be a very interesting information.
We're not using the MVVM pattern with our grids, as the "traditional" way of loading and displying data is sufficient enough for us. Some of our grids contain 100k+ values, the performance of the grid is imho always ok. The controls disn't look like they had a build in support for MVVM, if you're trying to use it it looks like you have to do everything manually. Maybe 10.2 changed things here, I haven't checked, but I don't think so.
We used our own implementation for localisation, so I don't know about the DX localization support.
我评估了几个WPF控件包，Telerik、devExpress、Xceed、SyncFusion等。我们主要对能够处理大量数据并且具有良好性能的网格控件感兴趣。在一个简单的测试中，我们将 120,000 个项目加载到网格中，并对字段进行分组。
与其他软件相比，DevExpress 的加载速度更快。加载需要 15 秒，而其他的都大约 45 秒。 DV 会在 7 秒内完成分组，而其他组则需要近 45 秒。其他几个控制包已锁定！ （仅供参考，数据是从 Mongo 加载的）。
当在 Telerik 上调出某个列的过滤器对话框时，它会延伸到屏幕底部之外，而没有任何滚动条。此外，单击下拉组合中的过滤器项目将立即执行过滤器，而不是等待我选择其他项目。因此，如果选择 5 个项目，则需要 5 倍的时间。
我希望 DevExpress 有一个复选框下拉筛选选项（如 Excel）。您只能选择一个值，但它确实有一个非常好的过滤器对话框，允许您执行更复杂的过滤器。尽管如此，还是希望能够轻松地检查一些值并快速继续。
Telerik 使用实体框架与 Sql Server 完美集成。它的分页、排序、过滤等功能直接与EF集成，并让Sql Server在数据库中完成这些操作。很不错！我在执行操作时监控了sql命令。如果您正在 sql server 上查看大量数据，这可能是真正能很好地做到这一点的一个控件。 （下拉过滤器组合除外，它不能很好地处理大数据）。我们使用 Mongo 来处理大数据，所以这不适用于我们。在测试数据时，Telerik 确实有一些例外。 DevExpress 没有分页选项，除非您自己设置。
最终我们选择了DV，因为数据量大且稳定的性能原因。
I evaluated several WPF control packages, Telerik, devExpress, Xceed, SyncFusion, etc. We were primarily interested in a grid control that could handle a large amount of data and have good performance. In a simple test, we loaded 120,000 items into the grid and did a group on the fields.
DevExpress was the fasting loading compared to the others. It took 15 secs to load, while the others where all about 45 seconds. DV would group in 7 seconds, while the others took nearly 45 seconds. A couple of the other controls packages locked up! (fyi, the data was being loaded from Mongo).
When bringing up the filter dialog for a column on Telerik, it would extend beyond the bottom of the screen without any scrollbar. Also, cicking on a filter item in the dropdown combo would immediately do the filter then rather than waiting for me to select the others. Therefore, if selecting 5 items, it would take 5 times as long.
I wish DevExpress would have a checkbox dropdown filter option (like Excel). You can only select a single value, but it does have a very nice filter dialog that allows you to do more complex filters. Still, would like to be able to easily check a few values and move on quickly.
Telerik integrated nicely with Sql Server using Entity Framework. It's paging, sorting, filtering, etc. integrated directly with EF and had Sql Server do these operations at the database. Very nice! I monitored the sql commands as doing operations. It you are viewing large amounts of data on sql server, this may be the one control that really does this well. (Except for the dropdown filter combo that does not handle large data very well). We are using Mongo for our large data, so this did not apply to us. We did have a few exceptions with Telerik when testing data. DevExpress does not have a paging option unless you it yourself.
In the end we chose DV due to performance reasons with large data and stability.
我肯定会选择 DevExpress，在我看来，他们的组件比 Telerik 的组件更好，并且具有更好的 API，那么我们不要忘记，您已经了解了 Windows 窗体世界中的对象模型、命名约定和 API，这不是一个小问题因为你很可能会重用你的专业知识，这更加重要和有价值。
I would definitely go for DevExpress, their components are in my opinion nicer and with better APIs than Telerik ones, then let's don't forget you already know their object model, naming conventions and APIs from the windows forms world, this is not a minor thing because you will most likely reuse your know-how and this is far more important and valuable.
Telerik RadDataGrid 支持 MVVM 和命令模式，开箱即用。 DevExpress 需要大量额外代码才能正确使用 MVVM。
The Telerik RadDataGrid supports MVVM and the command pattern properly straight out of the box. The DevExpress one requires a lot of extra code before you can use MVVM with it properly.
DevExpress WPF 很慢并且没有优化性能。我尝试过 DevExpress 和 Telerik 的富文本编辑控件。 Telerik 控件在性能方面优于 DevExpress。
DevExpress WPF is slow and not optimized performance wise. I've tried rich text edit control of both DevExpress and Telerik. Telerik control outperforms DevExpress in terms of performance.
我同时使用 Telerik 和 DEVExpress。根据我的经验，DevExpress在win表单控件方面更好。但是，Telerik 比 Asp.NET 控件更好。
DevExpress 在服务器控件上的渲染结果在客户端站点上非常混乱。他们使用表标签创建按钮控件。
I am using Telerik and DEVExpress both. Based on my experience, DevExpress is better in win form controls. But, Telerik is more better than in Asp.NET controls.
DevExpress rendering result on the server controls are very messy in client site. They create button control using the table tag.
几个月前，在评估新 WPF 项目的 WPF 控件时，我也处于完全相同的位置。我不确定您是否已做出任何决定，但我可以提供我使用 Telerik 的经验，希望对您有所帮助。
在我的项目中，一个特殊的需求是使用 TreeListView，并且提供此控件的知名供应商有限。我花了一些时间进行研究，发现 Telerik 可以满足我的需求。我下载了试用版并使用了 2 个月，联系了他们的支持人员，查看了他们的论坛。我可以告诉你，他们有很好的支持！通常支持人员会提供带有示例代码的解决方案。像所有开发人员一样，我们会遇到障碍，我们研究了 API、文档和示例。对我来说，支持很重要，因为它可以节省开发时间！我的反馈是 Telerik 提供了出色的 UI 控件、大量的集合和自定义选项以及出色的技术支持。然而，他们的文档并不是那么好。另外，请注意 WPF 控件中的性能，我的经验是，如果您有大型数据源，它会对性能造成一些影响。如果性能是关键要求，请务必在关键架构领域制作一些原型。
只要尝试一下，看看它是否满足您的需求。
顺便说一句，我也是 ComponentOne 的客户。如果可以节省您的时间，只需获取您需要的控件即可。重要的是这有助于按时运送您的产品！希望这有帮助。
I was exactly in the same position few months ago when evaluating WPF controls for a new WPF project. I’m not sure if you have made any decision, but I can offer my experiences with Telerik and hope it helps.
In my project, one particular need was to use TreeListView and there were limited reputed vendors provided this control. I spent some time doing researches and found Telerik which offered for what I needed. I downloaded the trial and used it for 2 months, contacted their support, checked their forums. I can tell you that they have excellent supports! Usually the supports provided solution with sample codes. Like all developers, we would encounter roadblock, we studied the API, documentations, and examples. For me, support is important as it saves development time! My feedback is Telerik provides great UI controls with vast collection and customization choices, and great technical supports. However, their documentation isn’t so good. Also, watch out performance in WPF controls, my experience is it has some performance hit if you have large data source. Be sure to do some prototypes in critical architectural areas if performance is the key requirements.
Just give it a try and see if it meets your needs or not.
BTW, I’m also ComponentOne customer. Just get the controls for what you need if it can save you time. The important thing is which helps ship your product on time! Hope this helps.
我会毫不犹豫地接受 Telerik...#1 原因是支持，#2 原因是如果控件不能满足您的需要，您只需提交一张票或在支持论坛上发帖，您就可以驾驶他们功能开发。
...很酷:)
I'd take telerik hands down...#1 reason being support, #2 reason is that if the control can't do what you need you just need to put in a ticket or post to the support forums and you can DRIVE their feature development.
...pretty cool :)
我相信devexpress在WinFormApp中确实更好。我已经使用它好几年了，真的很好。
另一方面，最近我尝试了它的 WPF 控件，它很糟糕，而且充满了包，我没有时间为这个项目切换到 Telerik。
我在 devex 中遇到的另一个问题是 RTL。如果您想拥有多语言应用程序，这可能很重要。
Telerik 可以支持 RTL，但 Devex 在 WinApp 中不支持它，在 Devex 中的 WPF 中也不完全支持它。
正如我所说，devex 在没有 RTL 的 WinApp 中更好。
I believe devexpress is realy beter in WinFormApp. I'm using it for several years it's really nice.
On the other hand recently I'h tried its WPF controls, It's terrible and full of bag I don't have time to switch to telerik for this project.
Another problem that I had with devex is RTL. If You want to have a multi language app It can be important.
Telerik can support RTL But Devex don't Support it in WinApp and in WPF in Devex don't supported it completely.
AS I said devex is better in WinApp without RTL.
从我的角度来看，与 Telerik 相比，DevExpress 提供了一些轻量级控件。使用 DevExpress 进行报告更加灵活。但与此同时，与其他工具相比，Telerik 具有更好的外观和感觉。
From my point of view DevExpress provides some what light weight controlls compare to Telerik. Reporting using DevExpress is more flexible. But at the same time Telerik having a better look and feel comapre to another tools.
我有一个朋友使用 Telerik 控件，他绝对信赖它们。他特别提到他们的数据网格控制是自切片面包以来最伟大的事情并且一直使用（这可能会根据您的第一个要点对您有所帮助）。
再说一遍，这不是第一手经验，但我相信他对此类事情的看法。
I have a friend that uses Telerik controls and he absolutely swears by them. He specifically mentioned how their data grid control is the greatest thing since sliced bread and uses all the time (which might help you out based on your first bullet point).
Again, not firsthand experience, but I trust his opinions on these kind of things.
还没有尝试过 DevExpress，但我使用 Telerik for WPF 它有一些很好的组件，例如 Gridview。但其他组件充满了错误，例如一个简单的停靠控件，迄今为止他们还没有设法让它正常工作。
have not tried DevExpress, but I use Telerik for WPF it has some good components the Gridview for example. but other components are full of bugs example a simple dockcontrol to this day they have not managed to get it to work properly.
我使用了 telerik wpf radcontrols 和 devexpress ！根据我的经验，我对 Telerik 控件感到满意，因为我的主要目标是提高工作效率并在短时间内提供具有良好用户体验的桌面应用程序！ Telerik 大量使用了 mvvm 模式并推荐使用它，因为他们的大多数演示都基于它！至于文档，查看演示源代码足以让我快速入门！另一方面devexpress更加成熟。换句话说，Telerik 包含错误，但如果您提出要求，支持人员总会为您找到解决方法。
I used both telerik wpf radcontrols and the devexpress ! From my experience i was satisfied with telerik controls as my main objective was to be more productive and deliver a desktop application with a good UX in a short time ! Telerik make heavy use of the mvvm pattern and recommend using it as most of their demos are based on it ! As for documentation looking at the demos source code was enough for me to have a quick start ! On the other hand devexpress is more mature. in other words, telerik contains bugs but The support will always find a workaround for you if you ask.