In the first part of this article we discussed how ASP.NET Profiles can help us extend SharePoint Server 2010 Audiences capabilities with targeting content to anonymous users. We discussed what ASP.NET Profiles are, how they work and how they can be configured with SharePoint Server 2010. In this part of the article we will extend the SharePoint Server 2010 Audiences so that they can make use of the data stored in ASP.NET Profiles.
SharePoint Server 2010 ships with the content targeting capability based on Audiences. Using this mechanism you can conditionally display content to groups of users based on their profiles. One shortcoming of this approach is that it needs user profiles which are not available on Internet-facing websites for anonymous users. However, using nothing more than the standard capabilities of the SharePoint framework and ASP.NET you can easily extend the standard content targeting mechanism to support targeting anonymous users.
Often when editing text, especially if you are a professional writer, you need some statistic information about the text you’re editing, like how many paragraphs or words you have already typed. While most desktop text editors, such as Microsoft Word 2010, provide you with such information, many Content Management Systems don’t offer such functionality. SharePoint Server 2010 is not an exception here. So if SharePoint is the platform for professional publishing it should contain this little nugget as well. Proudly presenting: Mavention Word Count.
SharePoint 2007 shipped with the STSADM command-line tool which was meant to be used for all kind of administration tasks like installing and deploying Solutions. Although the STSADM is still available in SharePoint 2010 for backwards compatibility the recommended way is to use PowerShell instead. SharePoint 2010 ships with a great number of PowerShell cmdlets which simplify the process of administering your SharePoint Farm. And although PowerShell is way more powerful than STSADM, it adds some extra complexity.
SharePoint Server 2010 ships with Audiences: a mechanism that allows you to target content to specific group of users. Audiences are a great capability: either if it’s from the e-commerce point of view of bringing the right products to the attention of the audience that is the most willing of buying it or if it helps you to unclutter the user interface by presenting just the right information. But how do you manage all that dynamic content?