With the Visual Studio 2012 getting released for public this week, it brings lots of great news & options for SharePoint 2010 developers. This article will highlight what’s new in Visual Studio 2012 for SharePoint 2010 development. Additionally, I will provide side by side screenshots for Visual Studio 2010 and Visual Studio 2012 for SharePoint 2010 development.
- Streamlined SharePoint project templates and item templates – Better organization of project templates and item templates to align with how SharePoint developers setup their projects and solutions. Many of the project templates in Visual Studio 2010 like visual web part, workflow, event receiver, list definition, content type, or site definition are most suited for project items. In reality, most of the developers used only Empty SharePoint Project for majority of new custom development in Visual Studio 2010. In Visual Studio 2012, Empty SharePoint Project has been renamed as SharePoint 2010 Project.
- Easily identifiable farm-only restricted project item templates – Unlike Visual Studio 2010, newer version of Visual Studio specifies farm level only project items – workflow, BCS model, application page, site definition, and user control to hint SharePoint developers which project items are supported in Sandbox solutions and which aren’t.
- New SharePoint List Designer – Allows you to create SharePoint lists visually using designer without CAML code
- New Content Type Designer – Allows you to create site content types visually using designer without CAML code and without manually generating complex GUIDs and inheritance of GUIDs for content types
- New Site Column Project Item Template and Site Column Designer – Allows you to create site columns visually using designer without CAML code and without manually generating GUID for site columns
- New Silverlight Web Part Project template and project item to streamline Silverlight coding
- Visual web parts supported sandboxed solutions – Visual studio no longer supports only farm level visual web parts. It no longer requires Visual Studio Power Tools add-ons for sandboxed visual web parts
- Improved IntelliSense support in Sandboxed solutions – Compile time errors for farm-only APIs. It no longer requires Visual Studio Power Tools add-ons for Sandboxed IntelliSense.
- New Publish Command for Local or Remote deployment – You can publish both farm level and sandbox SharePoint solutions to a remote or local SharePoint server file system using new Publish to File command. Additionally you can publish only sandbox SharePoint solutions to the remote or local SharePoint site using new Publish to SharePoint Site option. This would allow deploying sandbox solutions on on-premises or SharePoint Online site directly specifying SharePoint Site URL. This will deploy Sandbox solution to the site solutions gallery. It is important to note that you still require local development environment to test and debug code using Visual Studio 2012 for SharePoint 2010. Also, please note that this new Visual Studio 2012 Publish command replaces Visual Studio 2010 Package command.
Side by Side screenshots for Visual Studio 2010 and Visual Studio 2012 for SharePoint 2010 development
- SharePoint 2010 Project Templates in Visual Studio 2010 – Cluttered choices
- SharePoint 2010 Project Templates in Visual Studio 2012 – Much cleaner choices
- SharePoint 2010 Project Items in Visual Studio 2010 with Visual Studio Power Tools for SharePoint 2010 Add-on – No distiction between Farm and Sandbox Solutions
- SharePoint 2010 Project Items in Visual Studio 2012 – Clear distinction between Farm and Sandbox Solutions
- SharePoint 2010 Project Commands in Visual Studio 2010 – Package Command
- SharePoint 2010 Project Commands in Visual Studio 2012 – Publish Command
- Beth Massi’s Channel 9 Video – What’s New with SharePoint Tools for Visual Studio 2012 – http://channel9.msdn.com/Blogs/funkyonex/Whats-New-with-SharePoint-Tools-for-Visual-Studio-2012
- What’s New for SharePoint Development in Visual Studio 2012 – http://msdn.microsoft.com/en-us/library/ee290856(v=VS.110).aspx
- SharePoint Developer Tools in Visual Studio 11 Beta – Part I: What’s New in SharePoint Developer Tools for Visual Studio 11 Beta – http://blogs.msdn.com/b/sharepointdev/archive/2012/03/01/sharepoint-developer-tools-in-visual-studio-11-part-i-what-s-new-in-sharepoint-developer-tools-for-visual-studio-11-beta.aspx
- SharePoint Developer Tools in Visual Studio 11 Beta – Part 2: Feature Enhancements to Support SharePoint Online Development – http://blogs.msdn.com/b/sharepointdev/archive/2012/03/22/sharepoint-developer-tools-in-visual-studio-11-beta-part-2-feature-enhancements-to-support-sharepoint-online-development.aspx
- SharePoint Developer Tools in Visual Studio 11 Beta – Part III: Tips and Tricks in SharePoint List Designer – http://blogs.msdn.com/b/sharepointdev/archive/2012/04/19/sharepoint-developer-tools-in-visual-studio-11-beta-part-iii-tips-and-tricks-in-sharepoint-list-designer.aspx
- Doug Hemminger’s SharePoint 2010 Development in Visual Studio 2012 – http://www.sharepointdoug.com/2012/08/sharepoint-2010-development-in-visual.html
As soon as Visual Studio 2012 has released, I been performing all the new SharePoint Development using newer version. Hope you would do same. This is no brainer!!!!