WindowsMicrosoft

NET on the language. This first stage of the compilation can occur automatically when the first page request, or it can be done in advance (a process known as pre-compiled). Compiled code file is the IL assembly. The second phase of the compilation comes just before actual implementation of the page. At this stage, the IL code is compiled into a low-level machine code your own. This stage is known as operational compilation 'exactly the right moment' (Just-In-Time – JIT) and it goes the same for all applications.

NET (including, for example, applications Windows). Fig. 1 shows this two-step process of compilation. Fig. 1. Compilation in ASP.NET Web-page compilation. NET is divided into two stages, with the aim of providing developers with user-friendly environment and mobility.

Before creating a low-level machine code compiler needs to know what operating system and basic equipment which will operate the application (for example, a 32 – or 64-bit operating system Windows). With two stages of compilation, you can create a compiled assembly code. NET and distribute it to more than one platform. ASP.NET applications do not require that you compile on every request Web-page. Instead, the IL code they created once and re-generated only if you change the source code and files its own machine code is cached in the system directory path that looks something like this: C: WindowsMicrosoft.NETFrameworkv2.0.50727Temporary ASP.NET Files At some point it code is compiled to IL, depends on how you build and deploy applications. If the application is created as a Web-project in Visual Studio, code is compiled to IL during the compilation of the project. But if it is created as not related to any project Lightweight Web-site, then the code of each page is compiled the first to request this page. But in fact, and in another case, a second phase of the compilation (which implies the transformation of the IL-code to machine code) the code is already the first execution.