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.
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.
If you have used the Visual Studio 2010 SharePoint Developer Tools you have probably noticed that there are multiple SharePoint Project Item Templates to create Web Parts from. Find out which of them make the most sense in what scenarios.
Custom Controls are invaluable when working with Web Content Management solutions on the SharePoint 2010 platform. Unfortunately they are pretty inconvenient to use with large portions of HTML markup. Find out how to create better controls in SharePoint 2010.
Visual Studio 2010 SharePoint Developer Tools simplify working with SharePoint 2010 projects. By introducing SharePoint Project Items (SPIs) the tools hide the internals of creating SharePoint packages and allow you to focus on the real work. However, when you start moving SPIs around, things might get complicated and break. Find out how to prevent yourself from spending hours on fixing stuff using the standard functionality of the new developer tools.