Gridview中的三层架构 [英] Three tier architecture in Gridview

问题描述

我正在使用三层体系结构.我的一个Web表单只有三列.因此，我在设计页面上使用Sqldatasource进行了更新，删除，选择，而没有创建类文件.在3层体系结构中，这是一个好选择.请建议我.

然后建议最好的oops概念对3层架构很有用

谢谢u

Hi,
I am using three tier architecture. One of my webform has only three columns. So I updating, Deleting, Selecting using Sqldatasource on design page with out creating class file. It is good one or not in 3 tier architecture. Pls suggest me.

And then suggest best oops concepts is useful for 3 tier architecture

Thank u

推荐答案

嘿Devusha您在类文件中写入的内容可以在数据层或调用存储区中写入.业务层仅包含业务逻辑属性层仅包含为每个字段设置的属性

Hey Devusha What ever U write in class file that You can write in data layer or call store Procedure From data layer it is Good.... but Business layer only contains business logic Property layer only contains Property get set for each field

我完全不同意. 3层应用程序是一个程序，该程序分为三个主要的分离层.在这里我们可以看到这些层如何增加代码的可重用性.
请参阅下面的文章以进行简要说明.
使用N层架构创建ASP.NET应用程序 [^ ]
带有ASP.NET MVC3的N层体系结构示例， WCF和实体框架 [使用C#的ASP.NET中的3层体系结构 [

I am totally disagree. 3-tier application is a program which is organized into three major disjunctive tiers on layers. Here we can see that how these layers increase the re-usability of codes.
Refer the articles below for brief description.
Creating ASP.NET Applications with N-Tier Architecture[^]
A N-Tier Architecture Sample with ASP.NET MVC3, WCF, and Entity Framework[^]
3-Tier Architecture in ASP.NET with C#[^]



--Amit

这篇关于Gridview中的三层架构的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！