As I wrote in January “WSS 3.0, SharePoint 2007 and Project Server SP1 support ends soon”. But today I discovered Microsoft has extended the support for installations of Windows SharePoint Services 3.0 SP1, Microsoft Office SharePoint Server 2007 SP1 and Project Server 2007 SP1.

The Microsoft Surface (the table, not the tablet) is a Windows Vista computer running the Microsoft Surface Shell. This shell is by default localized for US English.

It is possible to localize for other locales, but there is no configuration screen to set the desired localization.

This article will summarize the different steps to localize the Surface shell.

If you want to develop for the Microsoft Surface (the table, not the tablet) you need a Surface device. But using the device to develop is not always practical, especially when there are more developers than Surface devices.

The solution for this is to install the Surface SDK Workstation Edition on your local development machine. This article will address some limitations you have to work around.

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.