Asp.net report Structure Learning Record, asp.net report structure

Asp.net report Structure Learning Record, asp.net report structure

When a compressed web Report project package is lying in my folder, I am totally confused. Asp.net, who has been studying java for a month, has never touched this aspect before. I have no idea where to start. (For other reasons, it is inconvenient to map and paste code)

There are also asp.net development and learning videos in hand, but they are not watched because of laziness. I collected a lot of information on the Internet and learned that such web reports are generally composed of three layers of physical architecture. (The following content focuses on projects in my hands)

Physical LayerLogic layer

Display layer: ui of the interface presented to the user

Logic layer: backend Data Control and Transfer BLL + DAL

Data Layer: Get and Change Database Data DBHelper

 

Data Layer

In order to have a certain understanding of the database, we should first start with the data layer. Data Layer web. DBHelper is useful in two databases, because there are two cs files OracleHelper. cs and SQLHelper. cs, opened with vs2010, because I have learned some java, so. cs code can be basically understood. These two files contain a lot of function overloading, knowing that they are used to receive SQL statements, sorting, and other parameters that are not clear about what to do, and to fetch or change data from the database.

 

Logic layer

DBHelper is clear, so we can see that the logic layer is divided into two parts: the business logic layer (BLL) and the data access layer (DAL ):

When you see some table fields in the business logic layer (BLL), you will know that this is integrating the QBE conditions and sorting, and passing the results to the data access layer (DAL ).

The data access layer (DAL) is filled with methods. These methods are written with SQL statements and uploaded to the data layer. Similar to: return new OracleHelper. GetDataByPage (..........);

I don't know if I can write the two contents together, but I don't know what it means to write them separately.

 

Display Layer

The display layer is really hard to digest because it does not understand xml, aspx, js, css, and html. In this project, each. aspx is called a page, and. aspx. cs contained in. aspx is called a Page code. The page is used to display content on the webpage, while the code controls the functions on the page. js is a script file, but you do not know how to use it. css is a style sheet, controls the display style of the content on the webpage. (Where. aspx. cs sends the submitted page content to the business logic layer (BLL). The master page (master) and control Ext used in the project can be understood as follows: the master is used in combination with the Ext control. aspx content page.

This part of the technology is still inadequate and will be discussed later.