WebPartZone Class
Allows you to create zones that are containers for Web Parts. The properties of this class allow you to specify how the zone will appear on your Web Parts page and also the behavior of the zone itself. For example, when you create the zone object, you can allow personalization and/or customization for the Web Parts placed within the zone.
System.Object
System.Web.UI.Control
System.Web.UI.WebControls.WebControl
System.Web.UI.WebControls.CompositeControl
System.Web.UI.WebControls.WebParts.WebZone
System.Web.UI.WebControls.WebParts.WebPartZoneBase
System.Web.UI.WebControls.WebParts.WebPartZone
Microsoft.SharePoint.WebPartPages.WebPartZone
System.Web.UI.Control
System.Web.UI.WebControls.WebControl
System.Web.UI.WebControls.CompositeControl
System.Web.UI.WebControls.WebParts.WebZone
System.Web.UI.WebControls.WebParts.WebPartZoneBase
System.Web.UI.WebControls.WebParts.WebPartZone
Microsoft.SharePoint.WebPartPages.WebPartZone
Assembly: Microsoft.SharePoint (in Microsoft.SharePoint.dll)
Available in Sandboxed Solutions: Yes
Available in SharePoint Online
The WebPartZone inherits the System.Web.UI.Control.ID property, which is a string value that is used to specify the programmatic identifier assigned to a WebPartZone control. The value of a WebPartZone control's ID property is used to assign the WebPart.ZoneID property of an instance of a WebPart class.
Another MS Sealed class.
Maybe Microsoft should look at un-sealing some of their MOSS classes, building them to be extensible. It would be good to be able to override the Chrome on a SharePoint WebPartZone for instance; you can do this in ASP.net, why can't you do this in MOSS? Many classes could benefit by just being un-sealed. There are hundreds of internal and sealed classes in MOSS.
- 8/6/2010
- Meat Popcicle