国际奥委会comparisions [英] IoC comparisions

问题描述

海洋学委员会考虑在开发ASP.NET Web应用程序项目，哪些是不同的IoC的优势是什么？

1. ObjectBuilder的
2. 统一
3. Spring.NET

解决方案

这是不是在你的清单，但考虑看的温莎城堡

设施等配套工厂，使本厂产品被注入而不是工厂本身或WCF设施注入的代理或创建一个主机的依赖数量。

有一个很好的流畅的界面，用于连接最多单个项目，但preferably你会使用一个约定自动线了，这样你就不必列出每一个组成部分。

其他的一些不错的功能：

• 要求，因为新版本的单个DLL。
• 支持注入通过SubDependancy解析器列表和数组

这里是一项民意调查，今年显示了国际奥委会的青睐拍摄。团结似乎是顶部，但认为可能是因为它是微软的产品和微软的研讨会将它捡起来默认情况下。

Which IoC to consider while developing ASP.NET Web application project and what are the advantages of different IoC?

1. ObjectBuilder
2. Unity
3. Spring.NET

解决方案

It is not in your list but consider looking at Castle Windsor

Number of facilities such as supporting Factories so that the factory product is injected not the factory itself or the Wcf facility for injecting a proxy or creating a host with dependencies.

Has a nice fluent interface for wiring up individual items but preferably you would use a convention to auto wire up so that you don't have to list each component.

Some other nice features:

• Requires a single dll since new revision.
• Supports injecting lists and arrays via SubDependancy resolvers

Here is a poll taken this year showing the favoured IoC. Unity seems to be top but that is probably because it is a Microsoft product and Microsoft workshops will pick it up by default.

这篇关于国际奥委会comparisions的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！