Unity 与 EntLib？
我使用 EntLib 一段时间了，最近发现了 Unity。乍一看，它似乎可以处理 EntLib 所做的大部分事情，但看起来更轻量级。
白天推荐哪一种、MVVM 架构以及其中一种的优缺点？
谢谢。
I've been using EntLib for some time, and have recently found Unity. At first glance it looks like it handles most everything that EntLib does, but seemingly lighter-weight.
Which is recommended for day, MVVM architecture, and pros/cons of one over the other?
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Unity是一个支持拦截的依赖注入容器。 EntLib 是一个包含 9 个应用程序块的库，Unity 就是其中之一。 EntLib 的范围更广泛，它处理其他横切问题 - 考虑日志记录、验证、异常管理、数据访问、缓存等。
早在 2008 年，当我们在 EntLib4.0 的工作期间设计 Unity 时，我们很快就意识到许多开发人员可以从中受益。这就是我们单独发货的原因。
EntLib5.0完全由DI驱动，默认使用Unity容器。如果您愿意，可以将其更换为另一个容器。 Prism 也是如此，它与容器无关。如果 EntLib 被设计为在应用程序的任何层中使用，那么 Prism 就是专门为构建复合 UI（在 WPF 和 Silverlight 中）而设计的。 EntLib 和 Prism 是互补的，而不是重叠的。
Unity is a dependency injection container with support for interception. EntLib is a library of 9 application blocks, one of which is Unity. EntLib has a much broader scope, it handles other cross-cutting concerns - think of logging, validation, exception management, data access, caching, etc.
Back in 2008 when we were designing Unity during our work on EntLib4.0, we quickly realized that it is something that many developers can benefit from by itself. That's why we shipped it standalone.
EntLib5.0 is fully DI-driven, and it uses Unity container by default. You can swap it out for another container if you wish. The same goes for Prism, which is container-agnostic. If EntLib was designed to be leveraged in any layer of your app, Prism was designed specifically for building composite UIs (in WPF and Silverlight). EntLib and Prism are complementary, not overlapping.
Unity是一个依赖注入容器和它自己的应用程序块；而 EntLib 是一组应用程序块，理论上 Unity 可以成为其中的一部分。
您还可以使用 Prism，它包装了 Unity/EntLib 和不同的块，以生成适合 Silverlight 和 WPF 中的 MVVM 开发的不同块的自助餐。
最初我想说的是使用 Prism 因为您已经熟悉 EntLib 并且可以使用 Unity作为你的 DI 容器。 Prism 还可以轻松地让您从不同的块中使用您需要的内容并忽略您不需要的内容。
Unity is a dependency injection container and its own application block; whereas EntLib is a grouping of application blocks which Unity could in theory be part of.
You also have Prism which wraps Unity/EntLib and varying blocks to produce a buffet of varying blocks geared towards MVVM development in both Silverlight and WPF.
Initially I would say head towards making use of Prism as you will already be familiar with EntLib and can make use of Unity as your DI container. Prism also easily lets you use what you need and ignore what you don't from the varying blocks.