ASP.Net Web Developer Guide |
||||||||
|
||||||||
Sitemap : Content in Chapter 1 |
Content in Chapter 2 |
Content in Chapter 3 |
||||||||
|
||||||||
Saturday, January 28, 2006
Compiling and Delivering ASP.NET Pages(Chapter 1)
The process of compiling and delivering ASP.NET pages goes through the following stages:
1. IIS matches the URL in the request against a file on the physical file system (hard disk) by translating the virtual path (for example, /site/ index.aspx) into a path relative to the site’s Web root (for example, d:\domains\thisSite\wwwroot\site\index.aspx).
2. Once the file is found, the file extension (.aspx) is matched against a list of known file types for either sending on to the visitor or for processing. 3. If this is first visit to the page since the file was last changed, the ASP code is compiled into an assembly using the Common Language Runtime compiler, into MSIL, and then into machine-specific binary
code for execution.
4. The binary code is a .NET class .dll and is stored in a temporary location.
5. Next time the page is requested the server will check to see if the code
has changed. If the code is the same, then the compilation step is skipped and the previously compiled class code is executed; otherwise, the class is deleted and recompiled from the new source.
6. The compiled code is executed and the request values are interpreted, such as form input fields or URL parameters.
7. If the developer has used Web forms, then the server can detect what software the visitor is using and render pages that are tailored to the visitors requirements, for example, returning Netscape specific code, or Wireless Markup Language (WML) code for mobiles.
8. Any results are delivered back to the visitor’s Web browser.
9. Form elements are converted into client side markup and script, HTML and JavaScript for Web browsers, and WML and WMLScript for mobiles, for example.
posted by Mr.Q at 1:12 AM
0 Comments:
Post a Comment
<< Home