ASP.NET 2.0 Web Part Vs SharePoint based Web Part

A nice comparisons between asp.net 2.0 custom webpart and sharePoint based web part.

ASP.NET 2.0 Web Part (System.Web.UI.WebControls.WebParts.WebPart)		SharePoint-based Web Part (Microsoft.SharePoint.WebPartPages.WebPart)
For most business needs. To distribute your Web Part to sites that run ASP.NET 2.0 or SharePoint sites. When you want to reuse one or more Web Parts created for ASP.NET 2.0 sites on SharePoint sites. To use data or functionality provided by Windows SharePoint Services 3.0. For example, you are creating a Web Part that works with site or list data.		When you want to migrate a set of Web Parts using the SharePoint-based Web Part infrastructure to Windows SharePoint Services 3.0. To create cross page connections. To create connections between Web Parts that are outside of a Web Part zone. To work with client-side connections (Web Part Page Services Component). To use a data-caching infrastructure that allows caching to the content database.

 

Windows SharePoint Services (WSS) V3.0 Web Part Infrastructure

The WSS V3.0 web part infrastructure uses many of the ASP.NET 2.0 web part control sets. The infrastructure also creates its own controls by inheriting them from the base class provided by the ASP.NET 2.0 web part control set.

There are three controls that make up the core web part infrastructure in WSS V3.0. They are SPWebPartManager, WebPartZone and WebPart.

Conclusion

Developers now have two sets of web part frameworks to work with. It is important to understand the difference between the two frameworks and when to use the appropriate framework to deliver wanted functionality.

…… HaPpY CoDiNg

Partha (Aurum)