Packaging dependent SharePoint projects – TFS Build 2010 tip #1

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.

Checking which Delegate Controls are activated on your site

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.

Automatically copying assemblies and symbols of dependent projects

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.

Inconvenient Excel REST Services and anonymous users

SharePoint 2010 ships with Excel REST Services that allow us to request pieces of Excel Sheets using a URL. Unfortunately things get pretty complicated when you try to make Excel REST Services available to your anonymous visitors. Find out how to deal with Excel REST Services and anonymous users.