blocks|key|4149192|text|我的观点是，企业库在大多数事情上都是过度设计的。不，我们不使用它，但我们的大多数项目都是短期的高流量网站，具有促销性质。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4149193|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It's my opinion that the enterprise library is over engineered for most things. No, we don't use it, but most of our projects are short term high volume web sites of a promotional nature.

blocks|key|1329263|text|%2B1表示过度设计。我们使用log4net而不是日志或异常处理块。我们使用原生.NET+System.Security命名空间，而不是entlib加密块。一些跟踪工具很不错，但我们在生产中没有任何使用它们的工具。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1329264|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

+1 for over-engineered. We use log4net instead of the logging or exception handling blocks. We use the native .NET System.Security namespace instead of entlib encryption blocks. Some of the tracing tools are nice, but we don't have anything in production that uses them.

blocks|key|1329250|text|不，我们不使用它。事实上，我是Enterprise+Library块的主要反对者，因为我已经看到太多与新发布的块的向后兼容性问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1329251|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

No, we do not use it. In fact I am a big opponent of the Enterprise Library blocks because I have seen too many backward compatability problems with new releases of the blocks.

blocks|key|29766|text|我们使用它(具体地说，Unity、日志和验证)，我不能说我是它的超级粉丝。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|29767|日志记录块无疑是过度设计的，具有讽刺意味的是，它仍然缺乏很多灵活性。令我惊讶的是，如果我想要将更结构化的日志记录消息写到DB中，而不是只写一个包含通用消息的表，那么我必须撕下和替换这么多代码。文档很粗略，很难理解记录器中实际发生了什么。|29768|不过，Unity实际上工作得很好。就我个人而言，我宁愿完全避免DI容器，但如果你必须使用一个，Unity看起来很好。|29769|我并没有真正参与到使用验证块的代码中，所以我不能告诉你它是如何工作的。|29770|但总的来说，我会说，是的，它是过度设计的，除非它能做你需要的开箱即用，否则你可能没有它会更好。|29771|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

We use it (specifically, Unity, Logging and Validation), and I can't say I'm a big fan of it.

The logging block is definitely over-engineered, and ironically still lacks a lot of flexibility. I was amazed at how much code I had to rip out and replace if I wanted to write more structured logging messages to a DB rather than just a single table with generic messages. The documentation is sketchy, and it's really hard to follow what actually happens in your logger.

Unity actually works ok though. Personally, I'd rather avoid DI containers entirely, but if you have to use one, Unity seems fine.

I haven't really been involved in the code that uses the Validation block, so I can't tell you how that works out.

But in general, I'd say that yes, it is overengineered, and unless it does exactly what you need out of the box, you're probably better off without it.

blocks|key|4149474|text|：企业库太过夸张了，它太复杂、太死板了。所以我们不用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|4149475|在我们的项目中(包括那些针对Windows+Azure上的分布式计算场景的项目)，我们使用作为轻量级的替代品。它插入log4net用于日志记录，Autofac+IoC用于配置，提供自定义业务规则，验证和异常处理(具有可靠性)应用程序块，同时将所有必需的程序集打包在几个dll文件中。|4149476|entityMap^0|1|Q|0|0|3X|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

Enterprise Library is an overkill. It is too complex and inflexible. So we don't use.

In our projects (including those that target distributed computation scenarios over Windows Azure) we use <a href="http://abdullin.com/shared-libraries/" rel="noreferrer">Lokad Shared Libraries</a> as a lightweight replacement. It plugs to log4net for logging, Autofac IoC for configuration, provides custom business rules, validation and exception handling (with reliability) application blocks, while packing all the required assemblies in a few dll files.

blocks|key|4149505|text|我喜欢从企业库中分离出来的旧的应用程序数据块。它非常简单，并且为您节省了大量时间。我们试着转移到Enterprise块，但不值得这么做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4149506|我们使用log4Net进行日志记录，效果很好。|4149507|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I like the old Application Data Block that was separate from Enterprise Library. It's very simple and saves you a lot of time. We tried moving to the Enterprise block but it wasn't worth the heft.

We use log4Net for logging and that works ok.

blocks|key|28991|text|我喜欢使用它，特别是对于小项目，因为它是一种“我不在乎，这个东西很简单，可以毫无困难地提供我需要的一切”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|28992|过度设计？怎么会这样呢？|28993|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I like using it, ESPECIALLY for small projects, because it's a "I don't care, this stuff simply works and provides everything I need without hassles".

Overengineered? How so?

blocks|key|28857|text|这一切都是以我相信的名字说的..“企业图书馆”企业非常大(是的，我知道，定义很好……但是，嘿，我现在有点醉了！)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|28858|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

it is all said in the name I believe.. "Enterprise Library"
Enterprise being significantly big (Yes I know, great defintion... but hey I am tipsy at the moment!)

blocks|key|29751|text|我使用它已经有一段时间了，但现在我转向了更灵活和更简单的解决方案，例如用于日志记录的log4net，用于数据访问的EF或Linq2sql等等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|29752|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have been using it for some time, but now I've turned to more agile and simple solutions, such as log4net for logging, EF or Linq2sql for data access and so on.

blocks|key|1331758|text|在做过许多大型网络项目后，我可以推荐来自ent库的缓存模块，因为它允许你通过简单的配置更改来使用nCache或类似的东西。这允许开发团队使用测试驱动开发，而不需要在任何地方安装nCache+(或类似的)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1331759|Log4Net比ent+lib日志记录块IMHO要好得多。|1331760|安全/密码学模块我已经用过几次了，通常我发现它们做了他们在罐头上所说的事情，而不是太繁琐或复杂。|1331761|框架的其余部分被其他更简单、更好的数据访问解决方案击败--+nHibernate、ActiveRecord、Tarantino|1331762|Unity+-+windsor、spring等|1331763|验证-我使用城堡堆栈|1331764|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

Having worked on a number of med-large web projects I can recommend the caching block from ent library as it allows you to use nCache or similar with a simple config change. This allows the dev team to use TDD without the need for nCache (or similar) to be installed everywhere.

Log4Net is far superior to the ent lib logging block IMHO.

Security / Crytography blocks I have used a few times and generally find that they do what they say on the tin without being too onerous or complicated.

The rest of the framework is beaten hands down by other simpler and (IMHO) better solutions
Data access - nHibernate, ActiveRecord, Tarantino

Unity - windsor, spring etc

Validation - I use the castle stack

In my shop we currently develop what I would consider small to medium sized projects. We have been investigating the Enterprise Library and how it may be able to help us in development. I have particularly been looking at the Logging block and comparing it with Log4Net. It seems to me that the Enterprise Library blocks would be an extremely over-engineered solution for something like simple application logging.

That being said. Are you using the Enterprise Library and on what size projects? What are your thoughts on the Enterprise Library as a whole? 

Thanks

Are you using the Microsoft Enterprise Library?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

在我的店里，我们目前正在开发我认为是中小型项目。我们一直在调查Enterprise Library，以及它如何能够帮助我们进行开发。我特别关注了日志记录块，并将其与Log4Net进行了比较。在我看来，对于简单的应用程序日志记录，Enterprise Library块将是一个非常过度工程化的解决方案。话虽如此。您是否在使用企业程序库，项目的规模是多少？作为一个整体，你对企业程序库有什么看法？谢谢

问您是否正在使用Microsoft Enterprise Library？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问您是否正在使用Microsoft Enterprise Library？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问您是否正在使用Microsoft Enterprise Library？
EN