When using SharePoint search in a Web Content Management (WCM) solution you are very likely to create your scope which will include Publishing Pages only. As other pages like Application Pages and Lists' Forms are not accessible by anonymous visitors you don't want them to appear in the search results on the public site. While creating what I call a 'public scope' is rather straight-forward there is one thing you have to keep in mind to make it work as expected.
While testing the newest feature of Imtech Fields Explorer - generated Content Types and Site Columns wrapper classes I have discovered that there were some issues while using these classes for referring to Site Columns. To avoid problems while referring to Site Columns from custom code I have decided to use SPField.Id instead of SPField.InternalName. While generating wrapper classes Imtech Fields Explorer v220.127.116.11 will now use the InternalName for the property name and Id for the value:
An important update to this version has been published. See Imtech Fields Explorer v18.104.22.168 for more details.
Andrew Connell has pointed today to a new white paper at MSDN Office Developer Center called How to Optimize SharePoint Server 2007 Web Content Management Sites for Search Engines. From what the title says I was expecting the paper to provide SharePoint specialists with SharePoint specific knowledge and solutions to various Search Engine Optimization (SEO) challenges. Unfortunately, the white paper published at MSDN has disappointed me.
Windows SharePoint Services v3 ships with a possibility to create RSS Feeds for every List. This feature is quite powerful as it allows you to create multiple RSS Feeds for one List based on Views. If you have worked with Lists at least a bit, you know that you can quite easily create a custom View using the standard SharePoint interface. Without any problems you will be able to define the filter and apply the sorting criteria.