After the ASP.NET project is deployed, the ASPX file is not compiled. This situation is maintained until the user's first access page, which is converted into CS, and compiled into a DLL, this time the accesses are not Soon, but since then, all visitors will get ideal access speed.
So how do you have all ASPXs that have been compiled into a DLL after deployment? Through the above description, it is not difficult to think, as long as you access all the pages, this access has a simple method, which is the folder where the project is located, transform the physical path to the HTTP address of the web access, and use HttpRequest to access it again. That is, if you have permission control, you may have to work more).
After access, the corresponding file is generated in /Winnt/Microsoft .Net/framework/ version number / Temporary ASP.NET FILES / project name / random number / random number, where * .cs are class files generated by ASPX. (After the file is processed, deployment without ASPX files), *. DLL is a DLL file generated by ASPX, *. RES is the residual part of the Runat = Server remaining in the ASPX file.
