SharePoint

.NET 3x ships with a number of new features among which lambda expressions: an easy way to write code for querying collections. Because of its ease of use many developers use it for retrieving data from different kind of collections. Just recently I’ve been asked to have a look how well lambda expressions perform while retrieving data from SharePoint comparing to SharePoint native mechanisms.

Yesterday I’ve found out about one of the new features of .NET 3.5 SP1: the renderAllHiddenFieldsAtTopOfForm setting which allows you to control where in the page the hidden fields are being rendered. Today I gave it a shot in combination with a SharePoint Web Content Management solution…

Microsoft Office SharePoint Server (MOSS) 2007 provides architecture for designing and developing scalable solutions. Two of these concepts are Site Collections for separating information and Variations for delivering multilingual solution. While working with both concepts – especially in Web Content Management (WCM) solutions I have found out that there is no easy way to create Site Collection or Variation relative links.

Imagine you want to retrieve the contents of a non-binary (text, CSS, XSL, etc.) file stored in SharePoint 2007 and all you know about that file is its location (URL). How would you do it?

As announced earlier this morning, Google has published the Search Engine Optimization Starter Guide: a set of good practices which can help you get the most of your website. Having it read with my SharePoint 2007 developer hat on a couple of things took my attention in particular.