ASP.net 2.0 's Web Part Framework

Asp.net|web

Recently asp.net 2.0 is no new news, no startling developments, in the absence of news, it appears that the priest had to create the news themselves, today is going to talk about the ASP.net 2.0 Web Part Framework.

The Web Part framework refers to the Web Component, why do you talk about it? There's a little story, and a reader asked me if he wanted to use the Web Part, but could you not use the SQL Server database? He asked me when I was a little stunned, because ASP.net 2.0 of things too much, so much so that I can not remember all the details, so I pulled out the 20th Chapter Web Part framework, I pull back to the Web Part framework of the composition of the operation of Memory, I'll tell him now in a minute. Why is the priest so sure? Please come and see how the Web Part Framework architecture is explained in the priest's book.

　　First look at the meaning and role of Web Components:

Web Components The English text is "Web Parts", the term is really confused at first glance, yes! It's really not intuitive what it is, the priest used the vernacular to interpret the concept, in fact the Web component is a bunch of predefined " Web Parts" ( I think part is more appropriate to turn the parts. And through these "Web Parts" so that users can make a patchwork of changes to adjust to the style of his favorite Web page and layout configuration (feel a bit like Lego blocks can be a free combination), unlike the traditional Web page content design is fixed, fixed is fixed! The user is the emperor Laozi or general manager to see the content and our small staff see is exactly the same, good point is all equal, bad point is not human nature, completely erase the different identity, sex, constellation users may like the appearance of style preferences; With Web Component users can combine the personalized mechanism to achieve their own set of appearance or style, and so on, user-customized Web component content will be stored in a personalized mechanism, even if the browser off the Web site, the next time the system will automatically from the personalized mechanism of the last time you defined the style, and apply it to the Web page you are logged into, how is it interesting?

　　Web Component Schema:

Before you explain the Web Component architecture Further, look at the following Web Component schema diagram.

　　Web Component schema Diagram

You can see a total of three layers from the above Web Component Architecture diagram: (1) The lowest level is the personalized mechanism (2) the middle tier is the UI structured component (3) the top-level is the Web Component UI control, the top layer will depend on the middle layer, and the middle tier is dependent on the bottom, what does that mean? Because they have to match each other to work. , as described below:

(1) Personal mechanism (lowest level)

Since Web Components allow users to customize the appearance of their personal preferences in the Web, style or composition, of course, there must be a mechanism for the user account to remember the various settings and changes made to the Web Components, so the "personalized mechanism" is the role of the user, and the next time users log in, The Web Component system will also automatically read the relevant data and settings from the personalized, and one by one revert to the user's previous set of Web page appearance settings.

(2) UI structured components (middle tier)

UI structural components are personalized and provide the core structure and services required by all Web Component controls. UI structured components consist primarily of two broad categories of things, one is the WebPartManager control, the other is zone, and each component page must have a WebPartManager control to manage and reconcile all the Web Component controls on this page, Zone holds the actual Web Component controls and is responsible for layout configuration of Web Component controls, as well as providing titles, skins, and styling to Web Component controls.

(3) Web Component UI Control (top-level)

The Web Component UI control is the actual rendering and function of the control, but it is only several types of "servo-side control", including: Web Component control, ASP. NET server control items, consumer custom controls, and custom server controls, and so on, which must be placed in a corresponding zone area container for management, the control on this layer relies on the reason for the middle tier.

So the WEB part has to rely on the personalization personal mechanism at the bottom of the hierarchy, and the individual must have a database, so I can answer him clearly in a minute! The Web part still requires a database.

Note: Because ASP.net 2.0 things are really too much, and the priest's memory is not very good, so really need a good technical manual for my reference, and for their reference to the technical manual to a better quality, and secondly deep breadth to be enough, three all the secrets of knowledge must be written out, there is no one in the prevention of their own bar ... Haha, so the priest has been telling you that this book is not only for your reference, but also the priest himself is an important reference, really not cover you, nor bluff, I have really often in the reference!