 |
|
|
|
|
|
ASP.NET Configuration
Using the features of the ASP.NET configuration system, the developers can configure all of the ASP.NET applications on an entire server, a single ASP.NET application, or individual pages or application subdirectories.
The authentication modes, page caching, compiler options, custom errors, debug and trace options, and etc. can be configured through the configuration files.
|
|
@Page Syntax
An ASP.NET page is defined as a file in a web application with an .aspx file name extension with an HTML form element that specifies runat="server".
Developers can optionally specify an @ Page directive or other directive (as appropriate to the type of page that you are creating), one or more Web server controls, and server code in the file.
|
|
Web Application Life Cycle
The life cycle of an ASP.NET application starts with a request sent by a browser to the Web server (typically IIS).
ASP.NET is an ISAPI extension under the Web server. When a Web server receives a request, it examines the file name extension of the requested file,
determines which ISAPI extension should handle the request, and then passes the request to the appropriate ISAPI extension.
ASP.NET handles file name extensions that have been mapped to it, such as .aspx, .ascx, .ashx, and .asmx.
|
|
ASP.NET Page Life Cycle
ASP.NET Page Life Cycle includes initialization, instantiating controls, restoring and maintaining state, running event handler code, and rendering.
|
|
|