托管扩展性框架（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是值得追求的体面大，15000小时严格的开发，应用程序？

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

推荐答案

我可能是错的，但我不认为MEF有任何情况下经纪业务。它类似于IOC容器，但面向更广泛的插件和应用程序的可扩展性的解决方案一般的合成引擎。 CAB和棱镜，另一方面是UI框架，使复合应用程序that're由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屋！