我们目前正在寻求采用某种类型的标准"开发人员框架，并已研究使用企业库.您会建议将这些模块用作软件开发的基础，还是我们应该自行开发?
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).
例如，我组织的一个项目是公司运营的核心，需要尽快开发和部署，并且会有很长的生命周期.出于这些原因，我们在 Enterprise Library 的帮助下选择了 CSLA.我们本可以选择其他框架，但重要的是我们选择了一个看起来很适合我们的应用程序和我们的开发人员技能集的框架，并且我们使用它来运行.
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.
是否有我们不使用的东西和我们可能不需要的开销?也许.但是，我会整天用它来换取尽早并经常在代码中交付业务价值.
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.
这篇关于企业库应用程序块还是自研框架?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！