Web Part framework of ASP. NET 2.0

Recent ASP. NET 2.0 has no new news, and there is no amazing news. In the absence of news, it seems that the priest had to create news by himself. Today we are going to talk about ASP. NET 2.0 web part framework. Web Part framework refers to Web Components. Why do we need to talk about it? The main story is that a reader asked me if he wanted to use a web part, but could he not use an SQL Server database ?! He asked me a little bit, because ASP. NET 2.0 has too many things, and I cannot remember the details of my residence. So I called out chapter 20th Web Part framework and pulled back the memory of the Web Part framework architecture diagram, I will tell him now in one minute ~ Impossible! Why is the priest so determined? Let's take a look at how the priest's book explains the Web Part framework architecture.
First, let's take a look at the meanings and functions of Web components:
The original English version of Web components is "Web parts". At first glance, this term is really confusing, right! It is really impossible to intuitively think about what it is. The priest first interpreted the concept in the vernacular. In fact, Web components are a bunch of pre-defined webpage parts (I think part turning into parts is more appropriate ), through these "webpage parts", users can splice and modify them to their favorite webpage style and layout configuration (it feels a bit like Lego building blocks can be freely combined ), unlike traditional web pages, the content is fixed after being designed, and the content is fixed! The content you see by the Emperor Lao Tzu or the general manager is exactly the same as that seen by our staff. The nice thing is that everything is equal, but it is hard to hear that it is not human, the style preferences that users of different identities, genders, and constellations may like. With Web Components, users can customize their own appearances or styles Based on personalized mechanisms, user-Defined Web component content is stored in the personalization mechanism. Even if you close your browser and leave the website, the system will automatically display the style you have defined from the personalization Mechanism upon next login, and applied on the Web page you log on to, how? Interesting!
Web component architecture:
Before explaining the Web component architecture, let's look at the following Web component architecture diagram.
Web Component Architecture
From the Web component architecture diagram above, we can see that there are three layers: (1) the bottom layer is the personalization mechanism (2) the middle layer is the UI structural component (3) the top layer is the Web component UI control item, what does the upper layer depend on the middle layer and the middle layer depends on the bottom layer? Because they must be paired with each other to operate, it is described as follows:
(1) personalization mechanism (bottom layer)
Since Web components allow users to customize the appearance, style, or composition of their personal preferences, of course, there must be a mechanism for memorizing the various settings and changes made to Web Components for user accounts. Therefore, the "personalization mechanism" plays this role. When a user logs on to the next time, the Web component system will automatically read the relevant information and settings from personalization, and then restore them one by one to the user's last set page appearance settings.
(2) UI structured components (intermediate layer)
The UI structure components depend on personalization and provide the core structures and services required by all Web component controls. The UI structured components mainly contain two categories: one is the webpartmanager Control item and the other is the zone, and each component page must have a webpartmanager Control item, in order to manage and coordinate all the Web component control items on this page, the zone is to accommodate the actual Web component control items, and is responsible for configuring the Web component control items by layout, and provide titles, appearances, and styles to the Web component control items.
(3) Web component UI control items (top layer)
The Web component UI control item is the control item for actual presentation and function. In fact, it is only a few types of "servo-side control items", including: Web component control items, Asp. NET Server control items Web component control items, user-defined control items and custom server control items, and these control items must be placed in the corresponding zone region container for management, therefore, the control item of this layer depends on the reason of the middle layer.
Therefore, according to this structural diagram, the Web Part must rely on the personalization mechanism at the bottom, and the personalization must be a database. Therefore, it is impossible for me to answer his question clearly within one minute! The Web part still requires a database.
Note: Because ASP. NET 2.0 is really too many things, and the priest's memory is not very good, so I really need a good technical manual for my reference, and the technical manual for my reference is good quality, and the depth of the second is enough, 3. All the secrets of knowledge must be written. No one is defending themselves... haha, so the priest has always told you that this book is not only for your reference, but also for the important reference of the priest himself. It is not for your reference, and it is not for your reference, I have been referring to it all the time!