用于内部工具的 WPF 或 WinForms? [英] WPF or WinForms for internal tools?

问题描述

在我的公司，我们为内部开发了许多工具，范围从简单的实用程序到成熟的编辑器.这些工具的优先级是稳定性、可用性和周转时间(意味着添加新功能的速度有多快).

At my company we develop a number of tools for internal that range from simple utilities to full-blown editors. The priorities for these tools are stability, usability, and turn-around time (meaning how quickly new features can be added).

到目前为止，我们一直在使用 WinForms，但绘图板上有几个新工具，我正在权衡是否应该继续使用 WinForms 或转向 WPF.当我们控制环境时，我们不必担心 .NET 版本等(尽管我们暂时必须在 XP 上运行).

We've been using WinForms up until now but there's a couple of new tools on the drawing board and I'm weighing up whether we should continue with WinForms or move to WPF. As we control the environment we don't have to worry about .NET versions etc (though we do have to run on XP for the time being).

我熟悉 WPF 提供的图形优势(基于矢量、硬件加速、皮肤能力)，但我想知道 WPF 是否还有其他方面可以证明它优于 WinForms.

I'm familiar with the graphical benefits offered by WPF (vector-based, hardware accelerated, skin-ability) but I'm wondering if there are any other aspects of WPF that make a compelling argument for its use over WinForms.

谢谢，

推荐答案

不要低估学习曲线.WPF 非常适合使用，但它可能是一场噩梦.我见过只有 WinForms 的开发人员对 WPF 比对 ASP.NET 更无助(即使对 Web 开发知之甚少).虽然大多数开发人员无需阅读任何书籍即可开始使用 WinForms 和 ASP.NET，并且在一定程度上提高了工作效率，但使用 WPF 似乎是不可能的.

Don't underestimate the learning curve. WPF can be really great to work with, and it can be a nightmare. I've seen WinForms only developers more helpless with WPF then with ASP.NET (even with very little knowledge of web development). While most developers were able to just start working with WinForms and ASP.NET without reading any books, and were productive to some level, this seems to be impossible with WPF.

不要忘记第三方组件.是的，市场上甚至还有新的参与者，而且在 .NET 3.0 e 之后多年.G.SoftwareFX 终于成功发布了他们的 WPF 图表解决方案(仅作为示例)，但 WPF 的组件市场仍然明显较小(商业和开源)，而且 WPF 组件通常仍然不如 WinForms 组件强大.

And don't forget about third-party components. Yes, there are even new players in the market, and years after .NET 3.0 e. g. SoftwareFX finally managed to release their charting solution for WPF (just as an example), but the component market for WPF is still significantly smaller (commercial as well as open source), and often WPF components are still less powerfull than their WinForms counterparts.

我同意架构，例如.G.数据绑定概念很棒，如果您遵循像 MVVM 这样的模式，但是 MSDN 中关于最佳实践 e 的文档很少.G.关于 MVVM，因此您必须亲自将您的团队指向网络上的文章和书籍等.

I agree that the architecture, e. g. the data binding concept, is great, if you follow a pattern like MVVM, however there is very little documentation in MSDN on best practice e. g. about MVVM, so you will have to point your team to articles on the web and books etc. yourself.

而且数据绑定在WinForms 2.0中已经非常强大，实际上非常相似.看起来很少有人知道并充分利用它.(可能是1.1才试过，觉得太复杂了……)

And data binding is already very powerful and actually very similar in WinForms 2.0. It just looks like few people know about and use it to its full potential. (Maybe they only tried it in 1.1 and thought that it was too complicated...)

这篇关于用于内部工具的 WPF 或 WinForms?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！