Tracking and analysis of page compilation during ASP. net2.0 Runtime

1. Access the page under a directory for the first time:
Asp.net will compile all pages under this directory and generate a temporary directory on the Web server (similar to the following path: C: \ WINDOWS \ Microsoft. net \ framework \ v2.0.50727 \ temporary ASP. net files \ Project name \ b9135081 \ af48f820 ).
Does it mean that if you want to enable the user to open the homepage quickly, you should not put too many pages in the home directory?

2. If you modify An ASPX file online:
Assume that app_web_mqhdhwjz.0.cs, app_web_mqhdhwjz.1.cs... And app_web_mqhdhwjz.dll are generated during the first user access.
After modifying its aspx file, it will delete the app_web_mqhdhwjz.0.cs, app_web_mqhdhwjz.1.cs... and generate a keystore file (it should mark that the DLL has expired );
And re-generate the corresponding aspx compilation file: app_web_htszrc400000.cs, app_web_htszrc400001.cs,... app_web_htszrc41_dll

These days I have been troubled by the problem of adding an HTM page to the ASPX page. This is now clear.
I have been discussing with Niels this afternoon. Why can I modify HTML to be immediately reflected in ASP after an HTML page is included in ASP pages, but not in aspx? Speaking of the issue of. Net compilation at runtime, we all think this is the cause!
Through the above tracking, we can draw a conclusion that the cause of this problem is indeed here:
ASP is interpreted, so after modifying the contained HTML, the client refreshes IE to see the effect;
Aspx is compiled after each modification of the corresponding file, and modifying the contained HTML does not cause aspx re-compilation, so the effect cannot be seen on the client. Unless you modify the aspx file that contains HTML, the modification will never be visible.