Web Parts


While Web Parts have become part of the toolkit for all ASP.NET developers,
currently Web Parts developed in ASP.NET 2.0 can’t be used in SharePoint (and
Web Parts built for SharePoint can’t be used outside of SharePoint). However,
Microsoft has committed to providing an upgrade to SharePoint that will allow
ASP.NET 2.0 Web Parts to be used in SharePoint in the near future.

The Benefits of Reusable Controls

1. Productivity: By creating reusable components, you don’t have to re-invent the wheel when implementing similar functionality in different applications (or parts of the same application).

2. Standardization: By using the same components to perform operations that are common to different pages, you are guaranteed that the functionality is implemented in a common way.

3. Simplification: By dividing functionality between specialized components and other parts of
the application (such as workflow management, business logic, data access), the complexity in any one part is reduced.

Framework Controls

1). WebPartManager: The control that enables a page for customization.

2). Zones: These controls define the sections of a page that users can customize. Different kinds of WebPartZones support different kinds of Web Part controls, as follows:

WebPartZone: For holding controls (either standard ASP.NET controls or controls that
you create).
CatalogZone: For holding Web Part framework controls that list the controls that you
can add to WebPartZones.
EditorZone: For holding editors that allow you to modify controls on the page.

3). Editors: The tools that allow the user to set properties on a control or otherwise modify a control.

AppearanceEditorPart: Allows the user to set the values of specific properties related to
the way that a control is displayed.
BehaviorEditorPart: Allows the user to set the values of specific properties on a control
in shared mode, which causes the changes to be made for all users instead of just for the
user making the change.
LayoutEditorPart: Allows the user to move controls from one location on the page to
PropertyGridEditorPart: Allows the user to set any custom properties on a control (that
is, those properties on a custom control that are not inherited from a base control).

4). Catalogs: The tools that list the controls that can be added to the page, including:

DeclarativeCatalogPart: Lists controls that are declared in the HTML in the page but
haven’t yet been added to the page.
PageCatalogPart: Lists controls that are already added to the page but aren’t visible to
the user (controls that are closed).
ImportCatalogPart: Lists controls that can be added to the page by importing from files
on your server.
ConnectionsZone: Holds connection objects that represent connections between controls in a Web Part Zone.

Read Users' Comments (0)