SharePoint 2010 ships with support for Linq. The great thing about it is, that Linq simplifies the process of querying lists and working with the retrieved items. Instead of objects, which you get if you’re using CAML, Linq retrieves for you strongly typed objects what makes it extremely easy to work with. And although it seems really perfect there are a few things that you need to keep in mind before you refactor your code to use SharePoint Linq instead of CAML.
One of the challenges while developing Internet-facing websites built on the SharePoint platform was rendering semantic breadcrumbs. Out of the box Office SharePoint Server 2007 was using for that purpose the ASP.NET SiteMapPath control. And while it looked okay visually, internally the whole control was rendered as non-semantic spans. SharePoint 2010 ships with a new control for rendering breadcrumbs called ListSiteMapPath. And while this control uses semantic markup and renders the breadcrumbs as an unordered list, the markup is too complex if all that you need is a simple list with some links. In such situation the Mavention Simple SiteMapPath can become very useful.
Mavention Export Page is a custom extension for the new Visual Studio 2010 SharePoint Developer Tools that allows you to export preconfigured Publishing Pages to XML which can be then used for provisioning pages with Site Definitions.
Do you still remember how many clicks did you need in Microsoft Office SharePoint Server 2007 to create a new Publishing Page? First you had to pick the New Page option from the Site Actions menu. Then you had to provide some information about the page and then finally, after pressing the OK button, you were redirected to the newly created page. SharePoint Server 2010 simplifies that process, but did you know that you can push it even further, and create new Publishing Pages with a single mouse click?
Recently I was presenting for a group of colleagues at Imtech ICT Integrated Solutions about new publishing features in SharePoint 2010. One of the questions that I got was: how can we leverage the Rich Text Editor for anonymous users on Internet-facing websites?