使用和不使用 Telerik 时 WPF 开发的生产力（例如）
这与我半小时前发布的问题相似但不同，WPF 开发比经典 ASP.NET（Web 表单）更快还是更慢。
我很好奇，如果我们在 WPF 项目中使用 Telerik（或 DevExpress 或 Infragistics 等），我们可以合理预期生产力会提高多少。这是一个足够大的项目，我们将有时间来加强我们选择的任何库。我们的应用程序将有一个围绕日历的相当复杂的 UI；否则它就很香草了。我们没有太多 WPF 经验。
我知道这取决于，尤其是。有多少控件是有用的，我们需要为我们的应用程序自定义它们多少，等等。
如果您可以（以某种方式）包含这些依赖项并得出某个数字，那就太好了。在我的梦里：
我用 和 完成了大型 WPF 项目 无需第三方控件库 （就我而言，是基础设施学）——以及 使用该库大约使我们的 生产力。
或者减半，无论您的体验如何。
This is kindred to but different from the question I posted a half hour ago, Is WPF development faster or slower than classic ASP.NET (web forms).
I'm curious about how much of a productivity boost we might reasonably expect, if we use Telerik (or DevExpress or Infragistics, etc) for our WPF project. It's a big enough project that we'll have time to ramp up on whichever library we select. Our application will have a fairly complex UI around a calendar; otherwise it's pretty vanilla. We don't have very much WPF experience.
I know that it depends, esp. on how many of the controls are useful, how much we need to customize them for our application, etc.
If you can (somehow) encompass those dependencies and arrive at some number, that would be great. In my dreams:
I've done large WPF projects with and
without a third-party control library
(Infragistics, in my case) -- and
using the library roughly doubled our
productivity.
Or halved it, whatever your experience is.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我的经验是，使用良好、干净的第三方控件集确实可以提高生产力，特别是如果控件集包含您的项目所需的功能。
例如，我目前正在使用 Telerik 的 WPF 控件，仅数据网格控件就可能将我们的总开发时间减少一半（对于需要它的特定项目），因为它会自动处理手动设置的麻烦事情使用标准 DataGrid 类。
话虽如此，如果我们没有使用该类，差异将会很小。仍然会有改进，特别是考虑到数据输入的一些改进（即：更好的数字控件），但变化不会那么引人注目。
不过，我建议您在选择产品套件时考虑学习曲线。例如，Telerik 的 WPF 产品具有相对较低的学习曲线，因为它们的设计与标准 WPF 控件非常相似。另一方面，我对 DevExpress 的 WPF 控件的体验却截然不同——几乎是相反的极端。 DevExpress 倾向于几乎完全使用其控制套件，并拥有适当的自定义工作流程。一旦您了解了这一点，就会感觉非常好 - 但它们与使用标准控件不同，并且在使用地点和方式方面往往相当普遍。根据我的经验，Infragistics 和 ComponentOne 处于这两个极端的中间。
My experience is that using a good, clean 3rd party control set does increase productivity, especially if the control set includes features which are required by your project.
For example, I'm currently using Telerik's WPF controls, and the Data Grid control alone has probably cut our total development time in half (for the specific project where it's needed), as it automatically handles things that are a pain to setup by hand using the standard DataGrid class.
That being said, if we hadn't used that class, the difference would have been minimal. There still would have been an improvement, especially given some of the improvements for data input (ie: nicer numeric controls), but the change would have been far less dramatic.
I would recommend, however, that you take the learning curve into account when choosing a product suite. Telerik's WPF products, for example, have a relatively low learning curve, as they are designed much like the standard WPF controls. My experience with DevExpress's WPF controls, on the other hand, are quite different - pretty much the opposite extreme. DevExpress tends to lend itself towards using their control suites nearly exclusively, and have a custom workflow in place. Once you learn this, it's quite nice - but they're different than using standard controls, and tend to be fairly pervasive in terms of where and how they're used. Infragistics and ComponentOne fall in the middle of these two extremes, from my experiences.
里德几乎说明了一切。只是想补充一下我的观点：
在 Winforms 时代，第 3 方控件集比 WPF 中更重要。对于我们的 WPF 项目，我们还没有发现任何我们自己无法完成的事情（也许除了 Actipro 的语法编辑器，它的实现相当复杂）或者没有提供与我们需要的完全一样的东西。所以这也是一个问题：
您是否需要套件中的所有控件，是否需要它们提供的所有功能，或者您是否需要比它们提供的更多功能？
或者您有时间和技能自己轻松编写它们吗？如果您发现自己经常重新设计这些控件，那么它们提供的功能是否比您自己所能提供的功能多得多，可能会产生疑问。
最后一件事：如果您没有太多的 WPF 经验，拥有这样的第 3 方库只能在一定程度上弥补这一点（如果有的话 - 您肯定可以创建蹩脚的 Telerik 软件）。 WPF 有一个相当陡峭的学习曲线，因此您可能首先尝试不使用任何第 3 方的东西，然后在发现无法执行某些操作时进行投资。
总结一下：我已经完成了使用或不使用第三方控件库（在我的例子中为 Actipro）的大型 WPF 项目 - 并且使用该库对于我们的粗略并不重要生产力。
Reed pretty much stated it all. Just want to add my opinion:
In Winforms days a 3rd party control set mattered a LOT more than in WPF. For our WPF projects we haven't yet found anything we couldn't do ourselves (well except maybe Actipro's Syntaxeditor which'd be fairly complex to implement) or which otherwise wasn't offered exactly like we needed it. So this is also a question of:
Do you need all the controls in the set, and also do you need all the functions they offer, or do you even need more than what they offer?
Or do you have the time and skill to easily write them yourself? If you find yourself restyling these controls a lot, it might be questionable if they offer so much more functionality than what you might be able to do yourself.
One last thing: If you don't have too much WPF experience, having such a 3rd party library will only make up for that until a certain point (if at all - you can certainly create crappy Telerik software). WPF has a fairly steep learning curve so you might at first try without any 3rd party stuff and invest if you find you can't do something.
so to sum it up: I've done large WPF projects with and without a third-party control library (Actipro in my case) - and using the library roughly didn't matter for our productivity.
和我一样。我们使用 Infragistics WPF 库进行图表和 DataGrid 的主要原因。我认为您选择的第 3 方库取决于您是否负担得起:)以及他们的支持有多好。已经使用 Infragistics 一段时间了，还可以（不是很好的支持）。
而且它确实提高了生产力，因为您不用再搞乱样板代码了
same with me. main reason we use Infragistics WPF libraries for Charting and DataGrid. I think the 3rd party library that you choose depends on if you can afford it :) and also how good is their support. have been using Infragistics for some time now, been OK (not great support wise).
And it def improved productivity as you dont have mess around with boilerplate code