Web Parts

What Is a Web Part?


Web Parts are prefabricated components that are basically targeted at easing the job of portal site / collaboration sites development.
They are basically server-side controls that run inside the context of special pages (known as Web Part pages) within an ASP.NET application or a WSS (Windows SharePoint Services) site.
Web parts combine the flexibility of user controls and custom controls. Developers can drag completed Web Parts from Web Part galleries and drop them into Web Part zones.
It can also be said that web parts add more value over other types of ASP.NET controls in that they add extra dimensions of user customization and personalization.

Webpart class when to use WSS webpart class and when to use asp.net webpart class?
Microsoft.SharePoint.WebPartPages.WebPart and System.Web.UI.WebControls.WebParts;

There are a few cases when you will have to use Windows SharePoint Services web parts instead of ASP.NET web parts. Windows SharePoint Services web parts support additional Windows SharePoint Services features that are not supported through an ASP.NET web part. Following is a list of features that are only supported through Windows SharePoint Services web parts:
• Connections between web parts that are outside of a Web Part zone
• Cross page connections
• A data caching infrastructure that allows caching to the content database
• Client-side connections (Web Part Page Services Component)
Another reason for using Windows SharePoint Services web parts is when you want to upgrade your Windows SharePoint Services V2.0 web parts to the V3.0 environment. The new version of the web part should be driven from the SharePoint web part class. SharePoint web parts can only be hosted in Windows SharePoint Services site pages.

WebPartManager roles:
• It tracks all the individual web part controls
• Also Tracks which Web Parts have been added to each particular zone.
• And stores and retrieves data about how each Web Part has been customized and personalized.
• It also initiates and tracks connections and communication between Web Parts controls.


Note:(One (and only one) Web Part Manager control is required for every Web Parts page.)