The SharePoint team has just announced that they are working on a tool which will help SharePoint developers to deal with disposable objects in custom code. SPDisposeCheck – as the tool is called, will check custom compiled assemblies and validate them against the Microsoft guidance.
Obtaining the value of a particular field (SPField) of a list item (SPListItem) is quite awkward. First of all you have to pass either the index, Id or the InternalName of an existing field. If the field exists a value of the object type is being returned. In some cases that value can be null. If it’s not you can cast it to its origin type as in most cases defined by the SPField.FieldValueType Property. Imagine doing all that each time you want to retrieve a field value. Isn’t there a better way?
I’ve just stumbled upon a new campaign called: “Give up and use tables”. Two guys: Todd A and Brian Matthews seem to be tired of wasting their time on making things work CSS. Instead they suggest using tables and even offer to provide you with the HTML code you need. To make it even better they provide a little app: a counter which measures how much time you already spent on making CSS work. Should you really be using tables for layout?
According to Microsoft Live Search it is neither the WSS or MOSS team nor the SharePoint MVP's that provide the most useful information on SharePoint. Looking for websites about SharePoint which provide RSS feeds Microsoft Live Search returns Wikipedia on the first place.
Recently I’ve stumbled upon an interesting challenge on the Microsoft SharePoint Forums: how to automatically page the content of a large Publishing Page? And while I came up with a plausible solution quite quickly I have decided to make it work as well.