复合应用程序块 - 是否有合适的替代品？
我有两个非常大的 WinForm 应用程序构建在现已失效的复合应用程序块上（“CAB”）来自 Microsoft Patterns &实践。我是较早采用者，并且第一个接受并使用 CAB。好吧，现在它确实已经死了，我开始越来越多地思考未来以及我可以迁移到什么框架。
我喜欢 CAB 的原因： * 结构、结构、结构——我很容易失去焦点，并且容易患上“分析瘫痪”。 CAB 引入了一种“做事的方式”，这让我能够走上正轨并开发应用程序，而不是担心“如何连接事件，或者最好的 IoC 是什么，等等。 * 实际上...我认为这就是我真正喜欢 CAB 的全部内容；0)
我看过有关“构建你自己的 CAB" 但我对此不感兴趣。我真的很想跳到一个类似的、可靠且得到积极支持的框架。我的网络搜索没有发现任何似乎能满足与 CAB 相同需求的内容。也许每个人都构建自己的框架，这就是为什么没有其他框架的原因。
如果您有任何指导或建议，我真的很想听听。
I have two very large WinForm applications built on the now dead Composite Application Block ("CAB") from Microsoft Patterns & Practices. I was an earlier adopter and jumped in first to embrace and use CAB. Well, now that it's truly dead I'm starting to think more and more about the future and what framework I can migrate to.
What I like about CAB:
* Structure, structure, structure - I lose focus easily and tend to suffer from "analysis paralysis". CAB introduces a "way to do things" and that keeps me on track and developing the application instead of worrying "how to wire up events, or what the best IoC is, etc.
* Actually... I think that's about all that I really like about CAB ;0)
I have seen articles about "build your own CAB" but I'm not interested in that. I'd really like to jump ship to a similar framework that is solid and actively supported. My web searches have not turned up anything that seems to serve the same needs as the CAB did. Maybe it's that everyone DOES build their own and that's why there isn't another framework out there.
If you have some guidance or advice I'd really like to hear it.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您可以查看
或
我不确定 SCSF 与 CAB 的具体功能/模式，但我已经使用 WCSF 一段时间了，它绝对提供您喜欢的 CAB 结构。
我相信这两项确实构成了 P&P 规定的指南，并且肯定会更新。
You can check out the
OR the
I am not sure about specific features / patterns that are targeted by especially the SCSF v/s the CAB but i have been using WCSF for a while now and it definitely provides the structure that you like about CAB.
I believe these two do constitute the prescribed guidance from P&P and are definitely being updated.
我建议您将应用程序移植到 WPF - PRISM 中。我希望他们也有 Winforms 的 PRISM 方式，但遗憾的是他们没有。我们最近使用 SCSF 迁移了两个企业级应用程序，现在出于显而易见的原因，我们已切换到 PRISM。它确实包括初始学习曲线，我知道 WPF 是什么，并且我的 Helloworld 应用程序只用了一些额外的东西就完成了。但现在由于我们不得不切换到 PRISM WPF，我正在对两者进行深入的学习！祝你好运！
I would suggest you porting your app into WPF - PRISM. I wish they had a PRISM way for Winforms too, but sadly they dont. We had two of our last enterprise level applications migrated using SCSF, now we have switched over to PRISM for the obvious reason. It does include initial learning curve, i knew wat WPF was and had my Helloworld app done with few extras. but now since we had to switch to PRISM WPF, i am having the steep learning on both! Good luck!