目前，我们正在采取一些类型的标准的开发框架，并已调查了使用企业库。你会推荐使用这些块作为软件开发的基础，还是应该做一些事情的土生土长的？

We are currently looking to adopt some type of "standard" developer framework and have looked into using the Enterprise Library. Would you recommend using these blocks as the foundation for software development, or should we do something home grown?

推荐答案

像所有优秀的答案架构和编程的问题，答案是看情况。

Like all good answers to architecture and programming questions, the answer is "it depends".

这取决于你的数据访问和对象设计的需求有多独特。它也可能取决于你计划如何支持你的应用程序在长期。最后，它在很大程度上取决于你的开发人员的技术水平。

It depends on how unique your data access and object design needs are. It may also depend on how you plan on supporting your application in the long term. Finally, it greatly depends on the skill level of your developers.

没有一个尺寸适合所有人的回答这个问题，但一般来说，如果你的主要重点是制造出的软件，提供了一些商业价值，挑选出一个现有的框架，并运行它。不要浪费你的周期建设的东西，不会马上带动企业利润（即提高收入和/或降低成本）。

There isn't a one-size-fits-all answer to this question, but generally, if your main focus is on cranking out software that provides some business value, pick out an existing framework and run with it. Don't spend your cycles building something that won't immediately drive business profits (i.e. increases revenues and/or decreases costs).

例如，我公司的项目之一就是核心，以公司的运作，需要开发并尽快部署，并具有较长的使用寿命。由于这些原因，我们选择了里昂证券与企业库一些帮助。我们可以挑其他的框架，但重要的是，我们选择了一个框架，看起来像它会十分符合我们的应用程序和我们的开发技能，我们跑了吧。

For example, one of my organization's projects is core to the operations of the company, needs to be developed and deployed as soon as possible, and will have a long life. For these reasons, we picked CSLA with some help from Enterprise Library. We could have picked other frameworks, but the important thing is that we picked a framework that seemed like it would fit well with our application and our developer skillset and we ran with it.

这给了我们一个很好的领先地位和社区从中我们可以得到支持。我们立即开始与提供的业务价值，并没有敲打我们的头撞墙试图建立一个框架的功能。

It gave us a good headstart and a community from which we can get support. We immediately started with functionality that provided business value and were not banging our heads against the wall trying to build a framework.

我们也是在这里，我们可以雇佣人对未来谁最有可能曾接触到我们的框架中的位置，给他们一个很好的领先地位。这将降低长期支持成本。

We are also in the position where we can hire people in the future who have most likely had exposure to our framework, giving them a really good headstart. This should reduce long-term support costs.

有没有一些事情我们不使用和开销，我们可能不需要？也许。但是，我会换了一整天在code创造商业价值的早期和频繁。

Are there things we don't use and overhead that we may not need? Perhaps. But, I'll trade that all day long for delivering business value in code early and often.