Visual Studio 2012 RC ships with the new SharePoint Development Tools. Unfortunately, once you pass the ‘F5’ experience and start working on some project you will notice that it’s not possible to just package your SharePoint 2013 project.
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.
Visual Studio 2010 SharePoint Developer Tools improve the development process on the SharePoint 2010 platform. By simplifying the packaging process they allow you to focus on the development rather than the packaging plumbing. Unfortunately, when working with larger solutions, it might get challenging for you to track which SharePoint Project Items are used where. Find out how to easier track the references to SharePoint Project Items with Mavention SPI References.
When extending standard functionality of SharePoint Project Item Types in Visual Studio 2010 SharePoint Developer Tools there are scenarios when you might want your extensions to be available on all types of SharePoint Project Items. Find out how to make your custom functionality available to all SharePoint Project Item Types.