Recently I got the task of creating a custom content aggregation Web Part which would roll up content from two lists. As this can be done in many different ways, I've decided to do a little research on which of these methods would perform the best.
Tired of navigating through the SharePoint jungle just to get to Site Settings, Style Library or the Master Page and Page Layouts Gallery? Remember this moment, because it's the last time you've done it. Proudly introducing: the SharePoint developer bookmarklets.
For the last couple of months I've been working with accessibility Web Content Management (WCM) in MOSS 2007. During that time I have gathered some do's and don'ts for working with accessible WCM solutions.
Every time you request a web page that doesn't exist, the web server provides you with a 404 (the web server response code for an non existing URL) page - an information page telling you that you've got it wrong. While some of your visitors, might be able to get to the information they are looking for either by correcting the URL or finding an alternative way to access the resource, it is a good practice to provide an information page which will help the average visitors to continue the navigation like nothing really happened.
While working with Control Adapters in either ASP.NET or SharePoint 2007 you will quite often want to intercept the output of the parent control and modify it before rendering. As retrieving the output is the same for each and every control I have created the following code snippet: