何去何从托管扩展性框架.NET？ [英] Whither Managed Extensibility Framework for .NET?

问题描述

有没有人与微软的托管扩展性框架（MEF）的工作有多大？还挺听起来像它试图将所有的东西给所有的人 - 这是一个附加的经理！这是鸭打字！我想知道如果任何人有与它的经验，积极或消极的。

Has anyone worked much with Microsoft's Managed Extensibility Framework (MEF)? Kinda sounds like it's trying to be all things to all people - It's an add-in manager! It's duck typing! I'm wondering if anyone has an experience with it, positive or negative.

目前，我们正在计划使用一个通用的IoC实​​施阿拉MvcContrib我们的下一个大项目。我们应该在混合扔MEF？

We're currently planning on using an generic IoC implementation ala MvcContrib for our next big project. Should we throw MEF in the mix?

推荐答案

我们的目标不是MEF是一个全功能的IoC。想想MEF的IoC的方面，最好的办法是一个实现细节。我们使用的IoC作为一个模式，因为它是一个伟大的方式来解决，我们正在寻找解决的问题。

We are not aiming for MEF to be an all-purpose IoC. The best way to think about the IoC aspects of MEF is an implementation detail. We use IoC as a pattern because it is a great way to address the problems we are looking to solve.

MEF集中于可扩展性。当你想到MEF的看它在服用我们的平台上向前迈进的投资。我们未来产品和平台将利用MEF作为一个标准的机制，增加可扩展性。第三方产品和框架也能够利用同样的机制。 MEF的平均用户，将创作的组件MEF将消耗并不会直接他们的应用程序中耗时MEF。

MEF is focused on extensibility. When you think of MEF look at it as an investment in taking our platform forward. Our future products and the platform will leverage MEF as a standard mechanism for adding extensibility. Third-party products and frameworks will also be able to leverage this same mechanism. The average "user" of MEF will author components that MEF will consume and will not be directly consuming MEF within their applications.

当你想扩展我们的平台在未来的想象，你把bin文件夹一个dll和你做。在MEF使应用程序亮起了新的扩展。这就是愿景MEF。

Imagine when you want to extend our platform in the future, you drop a dll in the bin folder and you are done. The MEF enabled app lights up with the new extension. That's the vision for MEF.

这篇关于何去何从托管扩展性框架.NET？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！