WebParts translate to compiled component controls that add personalization features on top. They are cool not in their default mode, but because of their enormous extensibility.
I don't think they replace IFrame based external pages, though. You should check out Darren Neimke's book on the subject - <http:// www.manning.com/neimke/> On May 9, 12:46 am, Arindam Sinha <[email protected]> wrote: > Hi, > We are working on a Portal site which consists of multiple pages > loaded in the home page. Those are basically loaded in Iframes/ASCX > controls (ASP.NET 1.1). Each of the pieces are called Portlets > (visually similar to Webparts). > Now to revamp and upgrade this, Webparts has been considered for > evaluation. > First priority is the perfromance benefits. Currently each of the > iframes holds pages from different Virtual Directories as well. Those > pages are loaded with huge data as well. Also, there are soem static > HTMLs loaded in some iframes. > So I want to know about the followings - > 1. Upgrading to ASP.NET2.0 with Web Parts will improve the performance > or not. Does web parts load individual webparts simultaneously? > 2. Hosting pages from different application (or virtual directories) > is possible in Webpartts? > > Also, any reference or case study is also highly appreciated.
