Rizzo stressed during his presentation at TechEd that users will have to start thinking 64-bit when they think of the next version of SharePoint.
The 2010 edition will require a 64-bit version of SQL Server 2005 or 2008. In addition, the server will run on the 64-bit version of Windows Server 2008.
Rizzo also announced that SharePoint Server 2010 will not support Internet Explorer 6.
It’s a best practice to have all custom code write to the event log. Every code execution should produce one and only one log entry. Exceptions (code speak for err) should be written here. For troubleshooting and support you can’t ask for a better tool. The framework exists, EventCombMT helps aggregate, and it allows you to run dozens … or hundreds … of apps while keeping a sharp eye on quality control.
If you see this error message in WSS chances are you have an active reference to custom field type but have not installed the field type. The “/_layouts/mngfield.aspx” page will throw this error in the above scenario. Two possible resolutions:
Visit Central Administration and deploy (or re-deploy) the WSP for the custom field type. For me this is usually http://www.codeplex.com/CustomFieldControls and the Parent Child Field types.
Remove the Site Column (SPField) objects with object model code. Requires developer skills.
Bill Buxton enthusiastically talks about the increasing importance of “experience” design. Tough times like this are breeding grounds for beautiful new ideas.