Template engine realization method used for Web development

Abstract

The invention discloses a template engine realization method used for Web development. The template engine realization method comprises the following specific implementation processes: designing multiple sets of general html templates for switching template styles; corresponding to different business pages to develop and design a HTML(Hypertext Markup Language) / XML (Extensive Markup Language) generator; operating business logics and data in advance, displaying a final result by the generated HTML, and dynamically displaying business data by the tag of the HTML; adding a style switching entry for background management to achieve a template switching effect; and revising contents in the template by interface design personnel, and revising the generator by program development personnel to finish the maintenance of a whole module. Compared with the prior art, the template engine realization method used for Web development has a simple integral realization process, C# codes are separated from a web page, so that convenience is brought for the long-term maintenance of a web system, and the template engine realization method has the advantages of being high in practicality, wide in applicable range and easy in popularization.

Description

technical field [0001] The invention relates to the field of computer technology, in particular to a practical template engine implementation method for Web development. Background technique [0002] Generally, the type of web page developed by the layered architecture of the Microsoft .net platform is aspx, and one cs file corresponds to one aspx page. The file structure of the source code cannot centrally manage the code that needs to be executed on the server side. During execution, because of the frequent execution of calling the server-side program to return to the front-end user data, the load on the server is heavier than that of the server. Since HTML and C# are mixed together, it cannot be easily retrieved; every time a page is accessed, the .net control must be loaded, which cannot The results returned by pre-running the control are not optimal in the static pages that provide access. Using pseudo-static can avoid the problem of sensitive information being passed t...

AI Technical Summary

Problems solved by technology

[0002] The type of web page developed by the layered architecture of the general Microsoft .net platform is aspx, and one cs file corresponds to one aspx page. The file structure of the source code cannot centrally manage the code that needs to be executed on the server side

During execution, because the server-side program is frequently executed to return to the front-end user data, the load on the server is heavier than that of the server. Since HTML and C# are mixed together, it cannot be easily retrieved; every time a page is accessed, the .net control must be loaded, which cannot The result returned by pre-running the control is in the static page that provides access, and the performance cannot reach the best. Using pseudo-static can avoid the problem of URL passing parameters and violent sensitive information. Interface designers can only focus on templates

Images