Now and again I come across code with hardcoded SharePoint IDs in it. Or scary loops matching a field, list or property name.
SharePoint provides some classes containing the out of the box IDs, you only have to know they exist.
I made an overview so nobody has to hardcode those pesky GUIDs, ContentTypeIds or property names any longer.

Working on a Project Server project we discovered it is quite easy to get issues with data integrity when users start retracting and deleting timesheets. After discussing the issue with Microsoft, they gave us a workaround which solves our problem.

The past couple of weeks I am working with Silverlight controls embedded in SharePoint 2007.
For one of the controls, I need to retrieve the data using the Search Query Web Service.

This was working perfectly in the development environment. But when deploying the control to the production environment it did not work.

The problem

With the introduction of the August Cumulative Update for SharePoint 2007 (KB973399) we encountered System.NullReferenceException: Object reference not set to an instance of an object. on all pages inheriting from MySitePublicWebPartPage.

Stefan Goßner reminds us of the fact that support for WSS 3.0 SP1, SharePoint 2007 SP1 and Project Server SP1 will soon end.