Principles: aspx and aspx. cs

In this article, we will talk about the aspx file.
Why is there aspx in ashx?
When using ashx, we also manually create an html template file, then read the template file in ashx, and then replace it first. The efficiency of the operation is not mentioned correctly, and the probability is very high. the important thing is that IO operations that are used during reading and replacement are resource-consuming. To avoid these troubles, we need to use aspx.

WebForm is divided into two files: aspx and aspx. cs.
Aspx is the content aspx and aspx of html + js + css on the template page. better Combination of cs, no need to operate c # code on the IO server to download all aspx. cs completely separates the server and client code
This "pre-aspx post-cs" method is called CoadBehind (post-code)
If there are very few widgets on the page, for example, a login page, we recommend that you use
Ashx: The execution efficiency of ashx is faster than the page lifecycle.

If the page contains a large amount of code and complicated business logic, you must use aspx.

The class generated by accessing the aspx and aspx. cs files in the program set.

 

 

 

Now let's talk about the operating principle of aspx.

 
The previous principles are exactly the same as those of ashx.
Here I will only talk about the request pipeline.

 

This figure only roughly describes the request principle and the details that can be added are not described.