DotNetNuke Skinning Whitepaper (technical part)

Translation: Technical

There are a number of ways to extract user interface elements from the page, each containing varying degrees of decomposition elements, and the need to integrate the presentation layer with the business layer. So define where, when, and how these decomposition elements are created to become the focus of the entire solution.

One technique that is popular in many scripting languages is to use tags or identifiers to describe dynamic functions in user interface files, which will be replaced by corresponding application logic when the page is loaded. Regardless of the method (intelligent decomposition, string function, regular expression, and so on) to complete this substitution, the key is that the Web application interface is generated when the page is processed, and if a replacement is performed after each request, performance will inevitably be affected. To mitigate this impact, the best solution requires the use of preprocessing or assembly techniques.

ASP.net provides a powerful abstraction of the Web page as a feature of a component. User controls are similar to the #include标志 in traditional ASP ... Apart from???. (Original: User Controls are similar to classic ASP #include directives ... except on steroids.) The latter did not know how to translate, who knows the advice to be grateful. User controls Enable separation User interface and reuse on different pages becomes possible. There are only two differences between a user control and an ASPX page: One is a suffix, the user control's suffix is ascx, and the other is that he may not contain