Guest_imported
New member
- Jan 1, 1970
- 0
Hi
I'm having trouble understanding life cycle of an application.
All the code-behind files are compiled into a single .dll file.The first time a user browses to the .aspx page, ASP.NET automatically generates a .NET class file that represents the page, and compiles it to a second .dll file. The generated class for the .aspx page inherits from the code-behind class that was compiled into the project .dll
file.This I know.But
---is this page's .dll file created everytime user sends request or does it exist for as long as app is running
---When user makes first request app starts running and ends only when Global.asax file is edited.But what is application here?
This .dll file that represents a single page or is it
code-behind .dll file or something else?
---I also can't see why ASP.NET is faster than ASP,since page is initialized, processed and disposed of every time a round trip to the server occurs.
I'm grateful for your help
I'm having trouble understanding life cycle of an application.
All the code-behind files are compiled into a single .dll file.The first time a user browses to the .aspx page, ASP.NET automatically generates a .NET class file that represents the page, and compiles it to a second .dll file. The generated class for the .aspx page inherits from the code-behind class that was compiled into the project .dll
file.This I know.But
---is this page's .dll file created everytime user sends request or does it exist for as long as app is running
---When user makes first request app starts running and ends only when Global.asax file is edited.But what is application here?
This .dll file that represents a single page or is it
code-behind .dll file or something else?
---I also can't see why ASP.NET is faster than ASP,since page is initialized, processed and disposed of every time a round trip to the server occurs.
I'm grateful for your help