WPF、Windows 窗体或其他什么? [英] WPF, Windows Forms, or something else?

问题描述

我们即将开始开发新产品.我们当前的产品是使用 VB.NET 编写的传统客户端-服务器 Windows 窗体应用程序.

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 窗体，我们是否会立即弃用?我认为它的上市速度会更快，但 Windows Forms 还会在五年内出现吗?

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?

我们应该从 Microsoft 产品迁移出去吗?我们所有的开发人员都是 .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屋！