ASP.Net Toolbox in VB .NET(WebParts Control): Part 6
In this article we will discuss, ASP.Net Toolbox controls and its uses. In this article I am only writing some lines on each and every control available in WebParts Control section.
Introduction
Here is Part 5
Toolbox is very-very important building block of .NET Framework. Toolbox is an area where all the controls existed. It helps the developer to develop any application very quickly, only drag the control from the toolbox and drop it on the form. To change its properties we have to select the control and make the properties changes from Properties window. We can do it manually by writing code-behind. There are over 100 controls available in ASP.NET 4.0. I am listing here all the controls available in ASP.NET 4.0 and writing some lines on each of them.
6. WebParts Controls:
This section includes features like personalization of website. Using the controls given in this section user can modify the content, appearance, styles, and behaviors of web page directly from web browser. User can personalize the web application dynamically without having developer or administrator rights. Such changes can be applied to entire web application or only to individual users.
- Pointer: It is just a pointer. If we drag any other control on form it causes to create that control on form but pointer does not create any control on form. In other word we can say, we select it for to ignore any other selected control.
- AppearanceEditorPart: This control is used to edit the appearance of an associated control on web page dynamically.
- BehaviorEditorPart: This control is used to edit the property that usually affects the behavior of an associated control.
- CatalogZone: This control is used to create catalog of Web Parts controls. Using this user can select controls to add on the page.
- ConnectionsZone: This control is used to provide user interface for to manage connections between WebPart and servers that uses WebPartZoneBase.
- DeclarativeCatalogPart: This control is used to provide simple way to developers to add server controls declaratively to catalog on the web page.
- EditorZone: This control is used to provide the end user to modify or personalize web pages dynamically without having developer or administrator rights. Such changes can be applied to entire web application or only to individual users.
- ImportCatalogPart: This control is used to provide the end user mechanism or user interface for accessing or uploading control's definition file to catalog.
- LayoutEditorPart: This control is used to edit the user interface properties and it affects the layout of WebPart. This control in only visible while WebPart page is in edit mode.
- PageCatalogPart: This control is used to provide the user flexibility to close or reopen the controls on WebPart page.
- PropertyGridEditorPart: This control is used to provide the end user functionality to edit custom properties on WebPart controls.
- ProxyWebPartManager: This control is used to provide developers a way to specify static connections in a content page when the WebPartManager has been specified in the master page.
- WebPartManager: This control is responsible for managing and coordinating all controls inside WebZones.
- WebPartZone: This control serves as the primary control in the Web Parts control set for hosting ASP.NET server side controls on a Web page.
Note1: Keep visiting to my articles, you will find different articles on different controls separately in coming days.
Note2: Continue in next part.
HAVE A GREAT CODING!