anurag_krishnaom

 Profile Answers by anurag_krishnaom 

• Oct 10th, 2007

 

First the page goes to server and server looks which type of engine should assign for this request( means which (engine) .dll will take care for this page there are several dlls which are catarized that which type of page will handled by this dll).
Engine handle the request and return the result to server and server return this result to client browser.

maverick_dude

 Profile Answers by maverick_dude 

• Dec 1st, 2007

 

An ASP.Net page consists of, at a  minimum, a single .aspx file and can contain other files associated also with the page. The .aspx file is called the content file as it has the visual content of the page.

When a browser requests a .aspx file from a web server, the server processes the page. If this is the first time that the page is being requested, ASP.Net runtime compiles from the page a Page class which is derived from System.Web.UI.Page class. The class is then compiled into an assembly, which is then actually run by the framework runtime to render the output to the client. The assembly is cached in the memory of the server, so that the subsequent calls to the page are serviced quicker as no compilation is required.

Praveen Chandra

 Profile Answers by Praveen Chandra 

• May 25th, 2011

 

Page Execution in asp.net life cycle is

1.PageInit()
2.Pageload()
3.Prerender()
4.Pageunload()