托管可扩展性框架 (MEF) 与复合 UI 应用程序块 (CAB) [英] Managed Extensibility Framework (MEF) vs. Composite UI Application Block (CAB)

问题描述

我们目前正在考虑将 CAB 或 MEF 用于我们的下一个应用程序.我没有看到有关如何为兄弟控件通信处理事件代理的 Codeplex 示例，也许我错过了.MEF中的控件间通信是如何工作的?

We are currently looking at either using CAB or MEF for our next application. I didn't see any examples on codeplex of how event brokering is handled for sibling control communication, maybe I missed it. How does inter-control communication work in MEF?

此外，我们计划使用 Infragistics，它为 CAB 框架提供了额外的组件.Infragistics 控件将如何集成到 MEF 中?

Also, we are planning on using Infragistics which has provided additional components for the CAB framework. How well will Infragistics controls integrate into MEF?

总的来说，MEF 是否值得追求一个相当大的、15,000 小时的严格开发、应用程序?

Overall, is MEF worth pursuing for a decently large, 15,000 hours of strictly development, application?

推荐答案

我可能错了，但我认为 MEF 没有任何事件代理.它是一个类似于 ioc 容器的通用组合引擎，但用于更通用的插件和应用程序可扩展性解决方案.另一方面，CAB 和 Prism 是 UI 框架，允许由 UI 组件组成的复合应用程序.由于 UI 组件很可能需要相互通信并响应其他 UI 组件中的活动，因此底层框架需要提供 UI 组件之间的事件(发布/订阅)机制.

I may be wrong but I don't think that MEF has any event brokering. It is a general composition engine similar to ioc containers but intended for a more general plug-in and application extensibility solution. CAB and Prism on the other hand are UI frameworks that allow composite applications that're made up of UI components. Since UI components will most likely need to communicate with each other and respond to activities in other UI components, the underlying framework needs to provide a mechanism for eventing (pub/sub) between UI components.

这篇关于托管可扩展性框架 (MEF) 与复合 UI 应用程序块 (CAB)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！