There are many ways to extract user interface elements from the page. Each method contains different levels of decomposition elements, and the presentation layer and business layer need to be integrated. Therefore, defining where, when, and how these decomposition elements are generated becomes the focus of the entire solution.
One of the most popular technologies in many scripting languages is to use tags or identifiers in user interface files to describe dynamic functions. When a page is loaded, these identifiers will be replaced by the corresponding application logic. No matter what method is used (Intelligent decomposition, string functions, regular expressions, etc.) to complete this replacement, the key is that the Web application interface is generated when the page is processed, if a replacement is performed after each request, the performance will inevitably be affected. To mitigate this impact, the best solution needs to utilize preprocessing or compilation technology.
ASP. NET provides powerful abstract web pages to become a component. User Controls are similar to the # include flag in traditional ASP... Except ???. (Original article: User Controls are similar to classic asp # include directives... Except t on steroids. I don't know how to translate it, but I am very grateful for anyone who knows it.) The user control makes it possible to separate the user interface and reuse it on different pages. There are only two differences between a user control and An ASPX page: one is a suffix, the user control is suffixed with ascx, and the other is that it can not contain <HTML>, <body>, or <form> label. There is almost no difference between other labels. A user control can insert a large number of files and separate the presentation layer from the application or background code. This feature allows you to create a large number of presentation layer files that reference the same background code. net is a compiled language. A page consists of a large number of compiled user controls, which makes the transfer efficiency quite high, much faster than the explain language.
Original article:
Technology
The specified action of user interface elements from a page can be accomplished using different strategies. each strategy invariably except des some degree of parsing to merge the presentation with the business logic. therefore, defining where, when, and how this parsing will take place becomes critical to the entire solution.
A popular technique employed in your script versions ages is to use tokens or identifiers in the user interface files to represent dynamic functionality. when the page is processed, the identifiers are replaced with the appropriate application logic. regardless of the method chosen to perform the replacement (ie. intelligent parsing, string functions, regular expressions, etc... ), The key point to emphasize in Web application Skinning is the phrase "when the page is processed ". if the replacement is being done on each page request, the performance of the application is going to be affected. to mitigate this performance impact, the optimal solution needs to take advantage of pre-processing or compilation technologies.
ASP. NET provides a very powerful feature for accessing acting web pages into individual components. User Controls are similar to classic asp # include directives... Snapshot t on steroids. user Controls allow you to isolate user interface functions and reuse them in other ASP. net pages. A user control is almost identical to a normal. ASPX page, with two differences: the user control has. ascx extension rather. aspx, and it may not have <HTML>, <body>, or <form> tags. user Controls can be broken into multiple files, separating the presentation from the application logic or "code-behind" file. this feature allows multiple presentation files to be created which can all reference the same "code-behind" file. and due to the fact that ASP. net is a compiled language, pages comprised of multiple user controls are assembled and rendered very efficiently-certainly faster than non-compiled or interpreted code.
Dotnetnuke skinning whitepaper translation record:
Dotnetnuke skinning whitepaper translation record (Introduction)
Dotnetnuke skinning whitepaper translation record (term and win Client Program)
Dotnetnuke skinning whitepaper translation record (technical part)
Dotnetnuke skinning whitepaper translation record (definition part)
Dotnetnuke skinning whitepaper translation record (dotnetnuke part)
Start building with 50+ products and up to 12 months usage for Elastic Compute Service
1 on 1 presale consultation
24/7 Technical Support 6 Free Tickets per Quarter Faster Response
Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.
A comprehensive suite of global cloud computing services to power your business
Payment Methods We Support
