Recently I have done some research on performance of various approaches to querying information from multiple lists. While reading Andrew Connell's book on WCM development I have discovered that I have missed one important approach. It turns out that it's probably the best bet in the most Web Content Management (WCM) solutions being often under heavy load. Curious about the results I have added it to my test project.
I'm a big fan of using the Explorer View: it provides you much more overview of the file system and allows you to access other directories with a single click even if they are located in a different branch on the file system.
Wow, Andrew Connell has just posted quite a comment on how CMS Watch has been reviewing SharePoint for the last couple of months. I've been following CMS Watch for a few months now and I have to agree with Andrew: there hasn't been a single positive word about SharePoint published by CMS Watch. For customers, who rely on their opinion and report, it might seem that SharePoint is nothing but an experimental CMS.
How many times did you actually have to rename the .wsp file to .cab in order to browse its contents? SharePoint 2007 allows you to use any extension for the solution files, so you could build all your solutions with the .cab extension to support quick browsing. This has however two downsides.
Microsoft Windows SharePoint Services (WSS) 3.0 introduces several new possibilities of controlling how the User Interface (UI) is presented to the users. While the mechanism has definitely been improved since the previous versions, there are a few things which doesn't make working with SharePoint easier to the end users.