页面处理
DotNetNuke使用单个ASPX页面( Default.aspx )来表现所有的控件和内容。这样做的好处有两个：一是集中了所有用户界面管理的逻辑在一个单一页面，二是减少与应用程序的交互接口以提高整个解决方案的安全性。Default.aspx 仅有相当有限的逻辑——仅包含了管理页面<HEAD>元素的代码和用来插入皮肤的占位符。
当用户首次访问DotNetNuke应用程序，DotNetNuke检查用户浏览器发送过来的请求报头以决定该载入哪个皮肤。这个过程需要访问数据库中的储存所有皮肤和容器分配信息的皮肤表。由于分配信息是以一种等级的结构存储的，所以子节点的皮肤信息可以取代父节点的皮肤信息（比如应用于频道等级的皮肤可以取代应用于站点等级的皮肤）。在请求数据库并返回正确的皮肤信息需要性能上的损耗，我们通过核心应用程序将有效的数据对象存储在缓存中的方法来减轻该过程的性能损耗。
一旦皮肤被识别，与其关联的用户控件就被动态的加载并取代占位符插入到页面中。每个界面的用户控件公用一个后台编码：位于\admin\Skins 文件夹下的skin.vb。这个文件执行了所有的皮肤处理过程，用来管理安全性以及插入内容。 原文：
DotNetNuke uses a single ASPX page ( Default.aspx ) for rendering all controls and content. The benefit of this approach is two-fold. First it centralizes all of the logic for management of the user interface in a single page. Second it reduces the number of entry points into the application which results in a far more secure solution. The Default.aspx has very limited logic – it includes code for managing the page <HEAD> elements and includes a placeholder for injecting the skin.
Page Processing
When a user first enters the DotNetNuke application, it examines the URL and request header it receives from the user's browser, to determine which skin it should use. This process requires a database request to the Skins table where all of the assignments for skins and containers are stored. The assignments are stored in a hierarchical manner so that child assignments are able to override parent assignments ( ie. a skin applied at the tab level should override a skin applied at the portal level ). The performance implication of making a database request to retrieve the current skin assignment for the page and modules is mitigated by efficient data object caching within the core application.
Once the skin is identified, the associated user control is loaded dynamically and injected into the page placeholder. Every skin user control must reference a common skin.vb code-behind file stored in the \admin\Skins folder. This file performs all of the skin processing for managing security and injecting content. 大厨师的翻译（重复劳动了-_-#）:DotNetNuke Skinning Whitepaper 翻译记录(页面处理部分)
DotNetNuke Skinning Whitepaper 翻译记录：
DotNetNuke Skinning Whitepaper 翻译记录(简介部分)
DotNetNuke Skinning Whitepaper 翻译记录(术语与win客户端程序部分)
DotNetNuke Skinning Whitepaper 翻译记录(技术部分)
DotNetNuke Skinning Whitepaper 翻译记录(定义部分--大厨师翻译)
DotNetNuke Skinning Whitepaper 翻译记录(DotNetNuke部分)
DotNetNuke Skinning Whitepaper 翻译记录(总揽部分)
DotNetNuke Skinning Whitepaper 翻译记录(文件组织部分--大厨师翻译)
Page Processing
DotNetNuke uses a single ASPX page ( Default.aspx ) for rendering all controls and content. The benefit of this approach is two-fold. First it centralizes all of the logic for management of the user interface in a single page. Second it reduces the number of entry points into the application which results in a far more secure solution. The Default.aspx has very limited logic – it includes code for managing the page <HEAD> elements and includes a placeholder for injecting the skin.
When a user first enters the DotNetNuke application, it examines the URL and request header it receives from the user's browser, to determine which skin it should use. This process requires a database request to the Skins table where all of the assignments for skins and containers are stored. The assignments are stored in a hierarchical manner so that child assignments are able to override parent assignments ( ie. a skin applied at the tab level should override a skin applied at the portal level ). The performance implication of making a database request to retrieve the current skin assignment for the page and modules is mitigated by efficient data object caching within the core application.
Once the skin is identified, the associated user control is loaded dynamically and injected into the page placeholder. Every skin user control must reference a common skin.vb code-behind file stored in the \admin\Skins folder. This file performs all of the skin processing for managing security and injecting content. 大厨师的翻译（重复劳动了-_-#）:DotNetNuke Skinning Whitepaper 翻译记录(页面处理部分)
DotNetNuke Skinning Whitepaper 翻译记录：
DotNetNuke Skinning Whitepaper 翻译记录(简介部分)
DotNetNuke Skinning Whitepaper 翻译记录(术语与win客户端程序部分)
DotNetNuke Skinning Whitepaper 翻译记录(技术部分)
DotNetNuke Skinning Whitepaper 翻译记录(定义部分--大厨师翻译)
DotNetNuke Skinning Whitepaper 翻译记录(DotNetNuke部分)
DotNetNuke Skinning Whitepaper 翻译记录(总揽部分)
DotNetNuke Skinning Whitepaper 翻译记录(文件组织部分--大厨师翻译)