Total Pageviews

Thursday, September 27, 2012

Understanding ASP.Net Pages-- dynamic complilation

Understanding dynamic complilation.

when u create an asp.net page, ur creating the source code for a .net class and u r creating an instance of system.web.ui.page class. then the entire contents of  an aps.net page including script, html are complied into a .net class.
when u request a page, ASP.net framework checks for a .net class that corresponds to the page. if the corresponding page does not exist, the framework automamtically compiles the asp.net page into a new class and stores the compiled class in the temporary asp.net files folder located as the

\windows\microsoft.net\framework\v4.0.3023\temporary asp.net files

the next time when a user requests the page , the compiled version is alwyas used until the source code is changed. the compiled version is stored in temporary asp.net files folder until the source code is changed.

When the class is added to the temp folder a dependency is created between the class and the original asp.net page, if the page is modified, the corresponding .ne tclass is deleted.next time any user has requested , the page is automatically compiled into a new .ne tclass.

This process is known as dynamic complilation, which enables asp.net applications to support thousands of users.


  u can precomplie the asp.net application by using aspnet_compiler.exe command line tool.

This process is

No comments:

Post a Comment