Setting the correct value for the FeatureId attribute of the ListInstance element is just one of things you can easily overlook on a sunny Friday afternoon when your mind is already enjoying the weekend. It’s like forgetting to read the small letters underneath a contract you’re about to sign: it seems like it all is going to be okay but at the end of the day you’ll be in troubles.
Recently I noticed that the customers ask for more control about the custom SharePoint solutions we deliver. They not only want to be able to customize general SharePoint settings which determine the working of the solution but they want to be able to configure various custom controls as well. Storing custom settings in a list provides the power users a nice interface, yet retrieving these values for each single request is very likely to decrease the overall performance. Is it then a battle between customizable and well performing or is there more to it?
Robert Chen of the Microsoft SharePoint Designer Team has yesterday shared with the SharePoint community some really valuable tips on how to make the custom controls work inside of SharePoint designer.
Branding Office SharePoint Server 2007 Web Content Management solutions reaches beyond development and is done in most scenarios by webdesigners. Once done the templates are being sliced into pieces and incorporated in SharePoint. To simplify the work, SharePoint community has created a Minimal Master Page: a template which contains all the elements required by SharePoint. Just recently I have noticed that using that template for branding is rather harmful and can lead to even more problems instead of sparing you the time.
It's probably a common knowledge by now, that the CQWP uses XSLT for creating the presentation layer for the queried data. The default set of the functions provided with XSLT is limited. While the ddwrt namespace adds some very useful functionality to the CQWP there are still many situations when you might need something else that isn't there like Regular Expressions for example. Many SharePoint developers I know would decide to create a custom Web Part at this point. Knowing how great the CQWP performs I would extend the standard functionality instead.