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.
We all know the Content Query Web Part shipped with MOSS 2007. It is so far the best content aggregation solution available. While it is extremely flexible and allows you to define your own presentation layer, it lacks some basic aggregation features like results paging and dynamic content filtering. While Andrew Connell has presented recently a nice approach to achieve last one, I have decided to focus on the paging functionality.
While working recently with the SPSecurityTrimmedControl I have found that it doesn't work as most of us would expect it to. The usage of the AuthenticationRestrictions and PageModes attributes took my attention in particular.
We all know more or less the SPSecurityTrimmedControl. It basically allows you to display its contents conditionally depending on the permissions of the current user. It is definitely a great piece of engineering and very helpful in various scenarios but what if it's just not enough and you need either to customize it or to create your own wrapper?
While working on numerous SharePoint projects I have noticed that there are particular settings I'm using and locations I visit quite often. Tired of the manual labor I have decided to wrap it all up in a SharePoint solution: Imtech SharePoint Developer.