Shortcoming, my ASP.net website development experience, welcome to participate in the discussion.

asp.net I have used the framework, the general experience of the following process:

1, at the very beginning, even the access to the database directly written in the codebehind, there is no layer of concept, there is no name space concept.

2, read some articles on the layering, improved a step (thought is 3-storey structure, but actually not):

Physical data tier (database/stored procedure)

Data access layer (not grouped by function function, no concept of class, no concept of attribute, no concept of domain, no concept of object-oriented, just set up a CS file, and then write the method of the data layer call)

Business Logic Layer (NO)

The presentation layer (thought to be the business logic layer, the method of calling the data access layer directly from the codebehind, simply invoking the method, never using the attribute)

With a bit of an enterprise-class name space concept, it's not deep.

Code naming rules are still confusing, and Microsoft's capitalization rules are not consistently recommended

The name of the datasheet and the name of the field is also confusing.

The stored procedures in the physical data layer are not written in a standardized and inefficient

3. Read Wrox's "ASP.net Web site advanced Programming Problem-design-Solution", in coding specifications and namespaces, naming rules to improve a step, the framework of the decision to imitate the book in the modules way.

Basically correctly implemented 3-layer structure design (data access layer, business logic layer, performance layer, a preliminary understanding of class design, attribute design, and learning to use a customized configuration file, and the use of the data access layer of the base class, to facilitate the invocation of stored procedures, coding efficiency.

4. Read the ". NET Enterprise Application advanced Programming section and Www.asp.net's aspnetforums design, for enterprise code generators and (Enterprise Object Builder) and the interface technology used in code, Non-codebehind technology (probably because of the use of component-type development?) , customizing server controls or overriding server controls, and so on, feels good, and you don't fully understand the benefits of using these technologies on your site's architecture.

5. Read some articles, the name of the scheme, the project name, and so on and have some new understanding.