development
Cleaning drop folder of Microsoft assemblies when building SharePoint Projects – TFS Build 2010 tip #2
When building SharePoint Projects using TFS Build 2010 many of standard available Microsoft assemblies are copied to the drop folder. This not only clutters your drop folder but also takes a lot of space on your disk. Find out how to remove all assemblies other than yours when building SharePoint Projects using TFS Build 2010.
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.
Microsoft SharePoint 2010 Enterprise Applications on Windows Phone 7–book review
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.
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.