Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Round trips to the server

Status
Not open for further replies.

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
 
1st Question:
The second dll is created only at the first request.

2nd Question:
the dll contains all the code behind and all the other non aspx files of your project. In the dll the language used is MIL. This gives the ability to the browser and server to compile the remaining part when the user requests a specific function or event and the JIT compiler (Just In Time) while compile only the code that manages that function or event.
This answers also the third question.

The first time a page is viewed, the compiled has to do some extra work and prepares the JIT compiler. After that, all the requests are faster.

hope this clears up =)
Daren J. Lahey
Just another computer guy...
 
I really apologize if I'm going to sound stupid,but I still don't completly get it.

-So if you have 10 aspx files in a project and there is a request to each one of them,then 10 .dll files will be runing until the app ends?

-So when a new request comes for the second or third time,the MSIL code of this .dll representing a page gets chanded only where it needs to be changed and the rest of MSIL code stays the same?

Thanks a lot
 
Can't someone answer my question and put my mind at ease?I really would like to know this

Thank you
 
Q) -So if you have 10 aspx files in a project and there is a request to each one of them,then 10 .dll files will be runing until the app ends?
A) -Yes all the 10 .dll files will be running but will be running untill the response is sent back to the clients.

 
Now I'm even more puzzled.Mr.Alcar said that the second .dll is created only at the FIRST request so I figured this .dll runs until app ends?Anyone?

Thank you for helping me
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top