|
I feel that if you want to perform template analysis completely in the background, it seems that waiting for the instrument to give up many advantages of .NET
First, replace the content in the HTML page, and then load some controls
This is a bit similar to what we are currently doing (this project is very BT, so I also hate it)
We implement self-analysis for each element.
That is to say, the work done by IIS and the browser is implemented by code, and the HTML code is directly output.
It is combined into an HTML page and displayed. This can solve the pre-processing of many controls in the background. But it has abandoned many advantages of .NET.
In fact, if the number of visits is not very large, you can put all the controls in a site, and each element has its own visit page.
In your INDEX. In ASPX, convert those tags you need to replace into URLs and use REQUEST to access the access pages of those elements. Replace the HTML from GET with INDEX. Those marks in HTM |
|