While working on new functionality for Imtech Fields Explorer I have noticed that there are Web Services in SharePoint 2007 which are missing the DISCO and the WSDL files. If you ever tried to attach a web reference to such Web Service you know that it will fail. While you might think that it's impossible, I have found a way of creating a WSDL file for an existing Web Service.
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:
Windows SharePoint Services (WSS) v3 introduces the concept of Site Columns: reusable fields which can be used for creating content definition across the whole Site Collection. While this concept allows you to manage the way content is stored, you have to be really careful when working with Site Columns in custom development.
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.