3层架构 - DAL，BAL，UI& Enterprise Lib 4.1 [英] 3-tier Architecture - DAL, BAL, UI & Enterprise Lib 4.1

问题描述

大家好，

我将在.NET 3.5和SQL Server 2008中使用3层架构（DAL，BAL，UI）作为后端实现桌面应用程序。在那，我计划使用Microsoft Enterprise Library 4.1。是否更适合使用？

任何人都可以使用企业库给我三层应用的样本/通用结构吗？这给我简要描述了3层如何与编码结构一起工作。

如果企业库不是优选的，或者你对3层样本有一些非凡的东西，你也可以建议其他实践。

解决方案

我曾经使用过企业库，如果我有选择的话，我不会再使用它了。
唯一能带来任何好处的部分是超重的膨胀者。
太少的利益无法证明。
您认为它会给您带来什么好处？

当您说桌面时。
您的意思是winforms或者您的意思是wpf ？
这是内部唯一且100％可靠连接吗？
什么样的数据吞吐量？

团队规模和营业额？
您是否需要TDD？

Hi to everyone,

I am going to implement desktop application with 3-tier architecture (DAL, BAL, UI) in .NET 3.5 and SQL Server 2008 as back-end. In that, i planning  use Microsoft Enterprise Library 4.1. Is it preferable to use ?

Can anyone give me sample/generic structure of 3-tier application with Enterprise Library ? That give me brief description that How exactly 3 layer works with coding structure.

You can also suggest other practice if Enterprise Library is not preferable or some extraordinary stuff you have for 3-tier Samples.

解决方案

I've worked with enterprise library and I wouldn't use it again if I had the option.
The only parts that offered any benefit were overweight bloaters.
Too little benefit to justify.
What benefit do you think it will offer you?

When you say desktop.
You mean winforms or do you mean wpf?
Is this internal only and 100% reliably connected?
What sort of data throughput?

Size of teams and turnover?
Do you need TDD or not?

这篇关于3层架构 - DAL，BAL，UI& Enterprise Lib 4.1的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！