DevExpress WPF控件的这个起诉书是否有效，什么是好的替代供应商？ [英] Is this indictment of DevExpress WPF controls valid and what is a good alternative vendor?

问题描述

我的公司正在使用DevExpress WPF控件开始一个主要的绿地开发项目。我刚刚阅读 WPF控件的这个批判性评论：

[...]开发WPF控件时，DevExpress开发人员完全误解了WPF。我真的不能很好地给你留下深刻的印象，那是多么令人不快的使用他们的控制。关于谈论一个具有这种消极性的供应商，我觉得绝对可怕（几乎有罪），但是他们在WPF套件中犯了一个严重的错误，在大约十年来开发软件方面，这是我最为沮丧的一个原因。

您是否同意DevExpress不了解WPF范例，并会在开发和维护期间使我们的开发人员感到悲伤？你能建议WPF控件的替代供应商吗？我正在寻找具有WPF控件的供应商，这将加强我们的应用程序，同时适合WPF API，绑定和MVVM。

---

关键博客文章的链接（上）已损坏。原作者已经表示：

我写了原文，并且决定在与他们交谈后以私人身份与DevExpress合作我很遗憾地决定删除这个职位。问候，Ira

解决方案

对于DevExpress而言，我感到非常失望。我失去了几个小时，试图简单地绑定一个组合框。下拉列表最多只会显示我的ItemsSource类名称多次。我甚至发布了一个StackOverflow问题，找出什么我可能做错了最后，我试图删除这一行xaml：

  devx：ThemeManager.ThemeName =DeepBlue
  

突然间我的问题消失了。它是由Developer Express wpf主题DeepBlue引起的。发现问题是一个巨大的救济。我公司现在将使用Telerik WPF控件。我的同事对DevExpress Asp.Net控件非常满意。这只是我们正在避免的WPF套件。

My company is starting a major greenfield development project using DevExpress WPF controls. I just read this critical review of their WPF controls:

[…] DevExpress developers completely misunderstood WPF when they developed their WPF controls. I really cannot impress upon you sufficiently well just how much of a displeasure it is using their controls. I feel absolutely terrible (almost guilty) about talking about a vendor with such negativity, but they have made a serious mistake in their WPF suite, it has been a singular source of the most abject frustration for me in about a decade of developing software.

Do you agree that DevExpress does not understand the WPF paradigm and will cause our developers grief during development and maintenance? Can you suggest an alternate vendor of WPF controls? I'm looking for a vendor with WPF controls that will enhance our application while fitting well with the WPF API, binding and MVVM.

---

The link (above) to the critical blog post is broken. The original author has stated:

I wrote the original article, and have decided to work with DevExpress in a private capacity after speaking with them so I have regrettably decided to remove the post. Regards, Ira

解决方案

Abject frustration is EXACTLY what I experienced thanks to DevExpress. I lost hours of my life attempting to simply bind a combo box. The drop-down list at best would only display my ItemsSource class name multiple times. I even posted a StackOverflow question to figure out what I could possibly be doing wrong. Finally on a whim I tried removing this one line of xaml:

devx:ThemeManager.ThemeName="DeepBlue"

Suddenly my problem went away. It was caused by the Developer Express wpf theme DeepBlue. Discovering the problem was a tremendous relief. My company will now be using Telerik WPF controls. My colleagues are quite happy with DevExpress Asp.Net controls. It is only the WPF suite we are avoiding.

这篇关于DevExpress WPF控件的这个起诉书是否有效，什么是好的替代供应商？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！