Export (0) Print
Expand All

ASP.NET WebParts controls

ASP.NET WebParts is an integrated set of controls for creating sites that enable end users to modify the content, appearance, and behavior of web pages directly from a browser. The modifications can be applied to all users on the site or to individual users. When users modify pages and controls, the settings can be saved to retain a user's personal preferences across future browser sessions, a feature called personalization. These WebParts capabilities mean that developers can empower end users to personalize a web application dynamically, without developer or administrator intervention.

WebParts are more complex than some of the other ASP.NET controls. For more information about WebParts, see the following topics in the MSDN library:

One UI structural component required on every WebParts page is the WebPartManager control. Although never visible, this control has the critical task of coordinating all WebParts controls on a page. For example, it tracks all the individual WebParts controls. It manages WebParts zones (regions that contain WebParts controls on a page), and which controls are in which zones. It also tracks and controls the different display modes a page can be in, such as browse, connect, edit, or catalog mode, and whether personalization changes apply to all users or to individual users. Finally, it initiates and tracks connections and communication between WebParts controls.

The second kind of UI structural component is the zone. Zones act as layout managers on a Web Parts page. They contain and organize controls that derive from the Part class (part controls), and provide the ability to do modular page layout in either horizontal or vertical orientation. Zones also offer common and consistent UI elements (such as header and footer style, title, border style, action buttons, and so on) for each control they contain; these common elements are known as the chrome of a control. Several specialized types of zones are used in the different display modes and with various controls.

ASP.NET WebParts Structural Controls

  • WebPartManager control   The WebPartManager control manages all WebParts controls on a page. One (and only one) WebPartManager control is required for every WebParts page.

  • ProxyWebPartManager control   The ProxyWebPartManager control exists for the particular scenario of declaring static connections in content pages when a WebPartManager control has already been declared in a master page. For information about programming the ProxyWebPartManager control, see ProxyWebPartManager Class Cc295265.xtlink_newWindow(en-us,Expression.40).png in the MSDN library.

  • WebPartZone control   Contains and provides overall layout for the WebParts controls that compose the main UI of a page. Use this zone whenever you create pages with WebParts controls. Pages can contain one or more zones.

  • CatalogZone control   The CatalogZone control contains CatalogPart controls (DeclarativeCatalogPart control, ImportCatalogPart control, and PageCatalogPart control). Use this zone to create a catalog of WebParts controls from which users can select controls to add to a page. For information about programming the CatalogZone control, see CatalogZone Class Cc295265.xtlink_newWindow(en-us,Expression.40).png in the MSDN library.

  • ConnectionsZone control   The ConnectionsZone control contains WebPartConnection controls, and provides a UI for managing connections. For information about programming the ConnectionsZone control, see ConnectionsZone Class Cc295265.xtlink_newWindow(en-us,Expression.40).png in the MSDN library.

  • EditorZone control   The EditorZone control contains EditorPart controls (AppearanceEditorPart control, LayoutEditorPart control, BehaviorEditorPart control, and PropertyGridEditorPart control). Use this zone to enable users to edit and personalize WebParts controls on a page. For information about programming the EditorZone control, see EditorZone Class Cc295265.xtlink_newWindow(en-us,Expression.40).png in the MSDN library.

  • ImportCatalogPart control   The ImportCatalogPart control provides the user interface (UI) for a user to upload a control's definition file (an XML file defined by a schema, that contains state information) to a catalog, so that the control can be added to a web page. The controls themselves do not appear in this type of catalog; the catalog is just a mechanism for accessing the definition files for external controls so they can be added to a page. For information about programming the ImportCatalogPart control, see ImportCatalogPart Class Cc295265.xtlink_newWindow(en-us,Expression.40).png in the MSDN library.

The WebParts UI controls, all of which derive from the Part class, comprise the primary UI on a WebParts page. The WebParts control set is flexible and inclusive in the options it gives you for creating part controls. In addition to creating your own custom WebParts controls, you can also use existing ASP.NET server controls, user controls, or custom server controls as WebParts controls.

ASP.NET WebParts UI Controls

  • AppearanceEditorPart control   The AppearanceEditorPart control provides an editor control that enables end users to edit several user interface (UI) properties on an associated WebParts control. For information about programming the AppearanceEditorPart control, see AppearanceEditorPart Class Cc295265.xtlink_newWindow(en-us,Expression.40).png in the MSDN library.

  • BehaviorEditorPart control   The BehaviorEditorPart control provides an editor control that enables end users to change properties that affect the behavior of an associated WebPart or GenericWebPart control. For information about programming the BehaviorEditorPart control, see BehaviorEditorPart Class Cc295265.xtlink_newWindow(en-us,Expression.40).png in the MSDN library.

  • DeclarativeCatalogPart control   The DeclarativeCatalogPart control provides a way for developers to add a set of server controls declaratively to a catalog on a web page. An advantage of using a DeclarativeCatalogPart control to create a catalog of server controls is that it does not require any coding. Page developers can work with the control entirely in the declarative (or page persistence) format, hence the name of the control.  For information about programming the DeclarativeCatalogPart control, see DeclarativeCatalogPart Class Cc295265.xtlink_newWindow(en-us,Expression.40).png in the MSDN library.

  • LayoutEditorPart control   The LayoutEditorPart control provides an editor control that enables end users to edit several user interface (UI) properties on an associated WebPart control. For information about programming the LayoutEditorPart control, see LayoutEditorPart Class Cc295265.xtlink_newWindow(en-us,Expression.40).png in the MSDN library.

  • PageCatalogPart control   Contains controls that have been closed on a page, and that can be reopened (added back to the page) by users. The controls in this type of catalog are controls that were already added to the page from another source, and were then closed by a user. For information about programming the PageCatalogPart control, see PageCatalogPart Class Cc295265.xtlink_newWindow(en-us,Expression.40).png in the MSDN library.

  • PropertyGridEditorPart control   The PropertyGridEditorPart control provides an editor control that enables end users to edit several user interface (UI) properties on an associated WebPart control. For information about programming the PropertyGridEditorPart control, see PropertyGridEditorPart Cc295265.xtlink_newWindow(en-us,Expression.40).png in the MSDN library.

Send feedback about this topic to Microsoft. © 2011 Microsoft Corporation. All rights reserved.

Community Additions

ADD
Show:
© 2014 Microsoft