本文介绍了DevExpress WPF控件的这个起诉书是否有效,什么是好的替代供应商?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我的公司正在使用DevExpress WPF控件开始一个主要的绿地开发项目。我刚刚阅读:

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






关键博客文章的链接(上)已损坏。原作者已经表示:


解决方案

对于DevExpress而言,我感到非常失望。我失去了几个小时,试图简单地绑定一个组合框。下拉列表最多只会显示我的ItemsSource类名称多次。我甚至发布了,找出什么我可能做错了最后,我试图删除这一行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:

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:

解决方案

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控件的这个起诉书是否有效,什么是好的替代供应商?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-29 18:27