This topic has not yet been rated - Rate this topic

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.

Namespace:  Microsoft.SharePoint.WebPartPages
Assembly:  Microsoft.SharePoint (in Microsoft.SharePoint.dll)
Available in Sandboxed Solutions: Yes
Available in SharePoint Online
[AspNetHostingPermissionAttribute(SecurityAction.LinkDemand, Level = AspNetHostingPermissionLevel.Minimal)]
public sealed class WebPartZone : WebPartZone, 
	INamingContainer

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.

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.
Did you find this helpful?
(1500 characters remaining)
Community Content Add
Annotations FAQ
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.