During ASP.NET Website Development a newbie has to understand the basic process of application and web page generation and their functional ways so I have made attempt to visualize these complicated processes in simple ways.

1. ASP.NET Website Development—Application & Page Life Cycle Part 1
If you are an end user of an application and requesting a web page, the process is simple. When you
enter the request on the browser, it will reach to the server. Server will understand it and process it in
order to generate web page. Once web page is ready, it will push to the browser of the client back and a
cycle is completed.
Here two things take place, one the application life cycle when a user triggers a web page request to the
server. Second is the web page life cycle when server triggers the web page formation process. Both
life cycles are finished when user gets web page.
Now, these simple things are a bit different at the ASP.NET developer’s point of view during ASP.NET
website development. At the moment user requests for the web page, application life cycle begins as
this request goes to the IIS. Now, IIS start checking the ISAPI extension in order to decide how to
handle the request. It will segregate paths based on the file type for instance it request is for an .aspx
page it will choose the path that leads to the ASP.NET engine. Once request reaches at the ASP.NET
engine it will check for the application domain because without application domain server will not run
the request so if it already exists ASP.NET engine will use it otherwise it will create a new one and pass
that request for further processing to the new application domain.
You might have question that why server need application domain. Actually, application domain
provides isolation level from the other websites, which are already exist on the server thus, it nullifies
any chance to get interference from other website requests. In Application Domain request is not
processing automatically, but it needs some objects to generate proper responses to the request. These
objects must have defined all things needed to create requested pages therefore, properties and class
definitions should be included in them.
In next part, we will see that which objects needed and what they should have.