SharePoint 2007 introduces various approaches to provisioning Web Parts instances in Publishing Pages. A few of them are:
Configuration provisioning is very important in structured and repeatable deployment of SharePoint 2007 solutions. While solutions which target intranet environments, tend to be more dynamic and consist mostly of assets, delivering Internet-facing sites using SharePoint 2007 is more about delivering a complete experience: preferably a preconfigured environment with all the assets on the right places. While SharePoint 2007 introduces Solutions and Feature - a framework for deploying assets, it doesn't provide a flexible mechanism for structured and repeatable configuration deployment. To be able to deploy SharePoint 2007 solutions in a fully structured and repeatable manner, we have designed our own approach for deploying configuration here at Imtech ICT Velocity.
Recently I have published the extended version of the Content Query Web Part which supports paging the results. As promised I'm going to provide a series of 'How I did it' articles to provide you some more details about my approach. In this article I will focus on getting the paging done inside the Content Query Web Part.
Developing custom Web Parts which leverage the concept of separating the presentation layer from the control provides you and your customer with great flexibility. Web Parts which produce XML output and render it using an XSL stylesheet given by the end user can be easily reused in multiple projects saving you in some cases some time. While working on the Extended Content Query Web Part I took a look at the performance of the XSL transforms and I have found out that there are thing to be considered while using that concept.