我应该在Prism- MEF或Unity中使用什么? [英] What should I use in Prism- MEF or 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.

推荐答案

它们是解决某些重叠场景的两种方法.

They are two approaches to solving some-what overlapping scenarios.

在开发模块化应用程序时，Unity会发光，其中用户将使用模块的子集，并且模块是独立的.

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便会亮起.

MEF shines when you have a lot of 3rd party developers creating plug-ins for your application - or several development teams publishing plugins.

我们从Prism的核心功能开始，稍后将为小部件类型的功能添加MEF，即边界线/特定于客户的功能将在MEF插件中提供.

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.

这两个框架都非常容易上手(MEF从一开始可能有点简单").

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.

这篇关于我应该在Prism- MEF或Unity中使用什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！