WebPart Life Cycle

Destin Joy

15y55k20100Article

The text of this article is not in this database — only its details are. The old site it was published on is gone, but the Internet Archive kept a copy: WebPart Life Cycle

C#.NET SharePointtutorialssharepoint articlesWeb PartLifecycle

2 Comments

Join the conversation! Your thoughts help the community grow.

Satya Arya15y ago
I am using lots of webparts created in sharepoint 2010. Now we decided that we will convert all webparts created in sharepoint 2010 into asp.net webparts becuase microsoft recommanded asp.net webparts. I have analyzed differences in both webparts, but unable to find key points which proves why should i use asp.net webparts instead sharepoint webparts? My webparts are very typicall having lots of business requirement. Thanks
- Destin Joy15y ago
  ASP.Net Web part • 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 of SharePoint SharePoint based web part • 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 Check the below links http://blogs.msdn.com/b/mab/archive/2007/02/28/asp-net-2-0-web-part-vs-sharepoint-2007-web-parts.aspx http://weblogs.asp.net/sbehera/archive/2008/07/09/asp-net-2-0-web-part-vs-sharepoint-based-web-part.aspx