Asp. NET page's server side

As a asp.net developer, you may be very clear asp.net how to handle code in an. aspx resource, how to parse the markup and dynamically convert it to a Visual basic® or C # class, and so on. But what happens next? Where is the asp.net generated file saved? How do I use them to meet page requests? From last month onwards, I began to pay attention to the process. In this month's content, I'll analyze what's happening on the server so that you can avoid some of the most common problem pitfalls. I'll discuss the storage of the asp.net temporary files and the dynamically generated source code for the class that provides the service for the page response. In addition, I will build a Resource Manager tool that can be used with any asp.net 2.0 or asp.net AJAX (originally code-named "Atlas") applications to view and debug the actual code of your page execution. But before you do this, you need to know a few things. (As with last month's column, this section is primarily based on the details of the asp.net working principles that are not documented.) These implementation details may change in future versions of the Microsoft®.net Framework. ）

What is stored in the temporary asp.net files folder?

The process of ASP.net page requests requires some temporary files to be used. When you install ASP.net 2.0 on a Web server, the folder hierarchy that you create is as follows:

%windows%\microsoft.net\framework\v2.0.50727

The version number here refers to the retail version of ASP.net 2.0. Each release version of the ASP.net (including each transitional build) has a unique version number, and a different folder tree is created to support concurrent execution of different versions. Therefore, it is extremely important that you specify the version of ASP.net that your application applies to. Applications running under ASP.net 1.x and ASP.net 2.0 are based on physically separate folders. Under the Microsoft.NET\Framework folder, you will find the same number of vx.x.xxxx subfolders as the number of installed ASP.net versions (see Figure 1).

Figure 1 ASP.net 1.0, 1.1, 2.0, and 3.0 run-time library files