我应该在 Prism-MEF 或 Unity 中使用什么？
Found several good(related) questions here and here but all are nearly a year old.
I will like to know in the current context of Prism development what is better or at least scenario where each is better.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
它们是解决某些重叠场景的两种方法。
当您开发模块化应用程序时，Unity 会大放异彩，其中用户将使用模块的子集，并且模块是独立的。
当您有很多 3rd 方开发人员为您的应用程序创建插件或多个开发团队发布插件时，MEF 就会大放异彩。
我们首先使用 Prism 来实现核心功能，稍后将添加用于 Widget 类型功能的 MEF - 其想法是边界线/客户特定功能将在 MEF 插件中提供。
这两个框架都非常容易上手（MEF 从一开始可能就“简单”一些）。
在我看来，这实际上更多地取决于您的开发策略的结构，而不是所讨论的应用程序。
They are two approaches to solving some-what overlapping scenarios.
Unity shines when you are developing a modular application where users will be using a subset of the modules and modules are self-contained.
MEF shines when you have a lot of 3rd party developers creating plug-ins for your application - or several development teams publishing plugins.
We started out with Prism for core functionality and will be adding MEF for Widget-type functionality later - the idea being that border-line/customerspecific functionality will be delivered in MEF-plugins.
Both frameworks are really easy to get started with (MEF probably a bit 'simpler' from the get-go).
In my oppinion it really depends more on how your development strategy is structured rather than the application in question.