Visual Studio 2010 SharePoint Developer Tools make it extremely easy to separate your solution into logical units and yet package them in a single SharePoint Package (WSP). Although building dependent SharePoint projects using Visual Studio 2010 is straight forward, building using TFS Build 2010 produces slightly different output. Find out how to build dependent SharePoint projects using TFS Build 2010 the right way.
Allowing users to rate your content is a great way of capturing feedback. SharePoint 2010 ships with the rating capability, which unfortunately at this moment doesn’t support rating by anonymous users. And this is exactly where Mavention Anonymous Rating comes in. Find out how to allow anonymous visitors to rate your content with Mavention Anonymous Rating.
Delegate Controls allow you to provide users with pluggable functionality which they can use to extend their existing solution without modifying the existing code. Unfortunately once enabled it’s difficult to track which Delegate Controls are used where on your site. Find out how to check which Delegate Controls are activated on your site using PowerShell.
Recently I had the opportunity of reviewing a new book on developing Windows Phone 7 applications that interact with SharePoint 2010 – Microsoft SharePoint 2010 Enterprise Applications on Windows Phone 7.
Using the new Visual Studio 2010 SharePoint Developer Tools you can package your SharePoint components into WSPs with just a few mouse clicks. And although it allows you to get productive and focus on the real work, this process has some limitations like not copying dependent assemblies to the output directory.