After several months of development of an ASP. NET application project, I had some experiences and shared them with you.
1. When static pages are available, static pages are used. Static pages do not need to be processed by ASP. NET, but are only processed by IIS. This is much more efficient than aspx pages. Pay attention to applications with high traffic volumes.
2. If you do not need to use session or viewstate for a page, you must disable it. Closing it is actually very simple.
Enablesessionstate = "false" enableviewstate = "false" if the session only needs to be read, enablesessionstate = "readonly"
3. Use as few server controls as possible. If yes, enableviewstate = "false" must be set for those that do not need to be saved.
After the development, the performance problem caused me a lot of trouble. After we deploy the service, the speed after we use the firewall is extremely slow (Nokia's firewall), which is more than 10 times slower than no firewall, the problem has not been solved yet. I don't know why. I hope to communicate with colleagues who have encountered the same problem.