WPF，Windows窗体，还是其他什么东西？ [英] WPF, Windows Forms, or something else?

问题描述

我们将要踏上新产品的开发。我们目前的产品是传统的客户端 - 服务器的Windows窗体使用VB.NET书面申请。

We're about to embark on development of a new product. Our current product is a conventional client-server Windows Forms application written using VB.NET.

是WPF准备好了商业应用？ 从我所看到的，现在看来似乎是很难开发一个用户界面使用WPF比它与Windows窗体。不过，我想速度带有经验。我有点担心，WPF可能无法赶上，虽然。

Is WPF ready for a business application? From what I've seen, it seems like it's harder to develop a user interface with WPF than it is with Windows Forms. But I suppose speed comes with experience. I'm a little concerned that WPF might not catch on, though.

我们是否应该留在Windows窗体？ 如果我们继续使用Windows窗体，是我们自己退居脱precation权开箱？我认为这将是更快地投入市场，但Windows窗体仍然是各地在五年内？

Should we stay with Windows Forms? If we stay with Windows Forms, are we relegating ourselves to deprecation right out of the box? I think it would be faster to market, but will Windows Forms still be around in five years?

如果我们从微软产品迁移出来？ 我们所有的开发人员.NET开发人员，以便迁移到另一开发环境可能是出了问题。

Should we migrate away from Microsoft products? All of our developers are .NET developers so migrating to another development environment might be out of the question.

我希望我有一个水晶球。

I wish I had a crystal ball.

推荐答案

我们花了一大笔钱，建立了我们最新的桌面电子商务完全包在WPF（除报告，我们互操作使用的ReportViewer）。我没有一天后悔。 WPF的声明方法是容易掌握适合所有人，它有助于加强UI的分离业务逻辑。

We took the plunge and built our latest desktop e-commerce package entirely in WPF (except for reporting, which we interop to use ReportViewer). I haven't had one day of regret. WPF's declarative approach has been easy to grasp for everyone, and it helps enforce separation of UI from business logic.

这是说，如果你的团队有很多经验的WinForms，那么它可能会适得其反花时间学习WPF。

That said, if your team has a lot of WinForms experience, then it might be counter-productive to spend time learning WPF.

如果这不是一个问题，给WPF一试，也许你会上瘾。

If that's not an issue, give WPF a try and maybe you'll get hooked.

这篇关于WPF，Windows窗体，还是其他什么东西？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！