SharePoint wallpapers - definitely a must-have for every SharePoint developer out there.
Matt Groves has just posted detailed information on costs of various SharePoint licenses. Although a bit difficult to read and to compare due to lack of formatting, it is definitely a very useful piece of information.
It's not that long ago since I released the previous version of the Imtech Fields Explorer. In that release I have introduced the possibility of exporting the Site Columns and Content Type definitions to XML using the GUI.
The Content Editor Web Part (CEWP) shipped with SharePoint 2007 is just one of these ordinary Web Parts: they don't introduce any extraordinary functionality, yet we all use them in our solutions for some reason. Because this Web Part is all about displaying the Rich Text you have entered, you might think, that it is almost impossible to mess that up. Unfortunately...
Recently I wrote about various approaches to provisioning Web Part instances in a structured and repeatable way. One of the approaches I have mentioned was using the AllUsersWebPart element within Feature manifest. While being manageable and flexible this approach has one big downside: it causes provisioning duplicate instances after the Feature has been reactivated (either by Activate-Deactivate-Activate or Activate using the -force parameter). In this article I present some possible approaches to prevent it and make your Feature provision always only one instance of each Web Part.