选择哪个 WinForms CompositeUI 框架？
我的团队在为我们公司开发头部应用程序之前几分钟就遇到了设计障碍。 我的团队使用 C#、.NET 3.5 开发 WinForms 应用程序。
在设计中我们需要做的第一件事是决定使用哪个 CompositeUI 框架。 嗯，首先我们确定我们将使用 CAB。 但考虑到 P&P 不再参与其中，这是正确的选择吗？ 雅典卫城呢？ 它足够稳定并且会在接下来的几年里一直存在吗？
所以这是我的问题：什么框架足够稳定并且适合在未来 3-4 年领导我的团队的应用程序？
需要你的帮助。 谢谢！
my team is minutes before developing the head application for our company and we ran into roadblock in our design. my team develops WinForms application in C#, .NET 3.5.
The first thing we need to do in our design is to decide which CompositeUI framework to use.
Well, first we were sure that we are going to use CAB. but is it the right choice considering P&P are not into it any more?? What about Acropolis? Is it stable enough and going to be here for the next few years??
So this is my question: what is the framework that is stable enough and is right for an application that will lead my team for the next 3-4 years?
your help is needed.
thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
如果您打算使用 WinForms，Smart Cient Software Factory 就是您的最佳选择。 从我在市场上看到的情况来看，大多数人正在放弃 WinForms 并转向 WPF。 目前我正在评估我的公司从 WinForms 迁移到 WPF 需要做什么。 我喜欢现在对 WinForms 的支持，但如果您的时间范围是 3-4 年，我强烈建议您查看 WPF 代替。
If you're going to do WinForms, the Smart Cient Software Factory is the way to go. From what I've seen in the market, most people are going away from WinForms and moving toward WPF. I'm in the process of evaluating what it will take for my company to move from WinForms to WPF at the moment. I love the support for WinForms right now, but if your time horizon is 3-4 years, I would strongly recommend you take a look at WPF instead.
如果您想无论如何坚持使用 Winform，有很多第三方解决方案（例如 Empinia< /a> 或 CodeProject 上显示的 Genesis 混合智能客户端框架除了智能客户端软件工厂。 这里的问题仍然是它们是否足够稳定并且有足够的耐力在 3-4 年内继续存在。
另一方面，如果您考虑的时间范围相当长，那么考虑 WPF 可能确实值得。 是的，这是一个学习曲线，而且 VS 2008 中的工具支持还不够完善。 但有了 VS 2010，情况会好很多，微软将在 WPF 上投入大量人力——VS 2010 本身就是用 WPF 编写的。
对于 WPF，有 Prism 形式的 P&P 指南，这是非常有前景的，看起来经过深思熟虑出去。 进入 WPF 还为您带来了额外的好处，即“免费”基本了解 Silverlight（它是 WPF 的一个子集，其核心）。 所以这可能是一个额外的好处。
马克
If you want to stick to Winforms by all means, there are quite a few third-party solutions out there (for instance Empinia or the Genesis Hybrid Smartclient Framework being shown on CodeProject) as well besides the Smart Client Software Factory. The question here remains whether they're stable enough and have enough stamina to still be around in 3-4 years.
On the other hand, if you're looking at this fairly long time frame, considering WPF might really pay off. Yes, it's a learning curve, and yes, the tool support in VS 2008 isn't quite up to snuff just yet. But things will get a lot better with VS 2010, and Microsoft will be investing a lot of manpower in WPF - VS 2010 itself is written in WPF.
For WPF, there's P&P guidance in the form of Prism, which is very promising and looks very well thought out. Going into WPF also brings you additional benefits of basically knowing Silverlight "for free" (it's a subset of WPF, at its core). So that might be an additional benefit.
Marc
Glenn Block 发布了一些 不久前的指南可能会引起人们的兴趣。
Brian Noyes 实际上将 PRISM 的部分内容移植到WinForms，但我不知道它是否足够好和稳定，可以作为您未来几年的平台。 =)
Glenn Block posted some guidelines a while ago that could be of interest.
And Brian Noyes actually did a port of parts of PRISM to WinForms but I don't know if it's good and stable enough to be used as your platform for the next couple of years. =)