Are you ready for SharePoint 2013?
This is the second in a four part series that provides a 35,000-foot overview of some of the major changes expected in SharePoint 2013. With this piece we will dive into what will be new for developers.
The series covers these changes as they relate to administrators, developers, designers and end users.
What’s New for Developers?
There are lots of changes coming to SharePoint 2013 that developers will need to know about.
Visual Studio 2012
SharePoint 2013 will include enhanced Visual Studio functionality. These enhancements include new Project/Feature/Package Properties, as well as new deployment options. Visual Studio 2012 also includes New Item Templates designed to work with SharePoint 2013, including SharePoint Applications (SPApps).
SharePoint 2013 introduces a corporate catalog and a public marketplace, which is essentially an app store. Developers can now write applications that extend SharePoint sites using the new SharePoint App Model. In SharePoint 2013, SPApps can be SharePoint hosted using a client web part, Azure-hosted (auto-provisioned or on premises), or developer-hosted using Chrome Control or OAuth.
SharePoint REST (Representational State Transfer)
SharePoint REST is a new service in SharePoint 2013 that allows you to interact with SharePoint artifacts. It provides support for CRUD (create, update, delete) operations from SharePoint Apps, solutions, and client applications using standard OData and REST web technologies.
Business Connectivity Services (BCS)
SharePoint 2013 has made External Content Types (ECT) from external lists accessible via Windows Communication Foundation (WCF) services or OData. This helps users more easily consume and interact with external data sources located outside of SharePoint. External List Event Receivers and alerts are also now available in SharePoint 2013 along with filtering, sorting, and support for REST (Representational State Transfer).
Remote Event Receivers
SharePoint 2013 will include Windows Azure Workflow (WAW) Services, which is built on Windows Workflow Foundation 4. Don’t worry. The 3.x legacy is still there for backwards compatibility, which isolates logic into a service that is independent of SharePoint. SharePoint 2013 also includes the AppFabric Workflow Model, which provides a lot more flexibility on the scalability of workflows.
SharePoint 2013 features NAPA, which is a browser-based environment that allows developers to build apps for the new cloud environment. It is an online companion to Visual Studio and can be used to create applications before fully migrating to Visual Studio.
Agaves are replacing Office add-ins in SharePoint 2013 to add increased functionality and customization. Agaves allow developers to create an Office App that hosts external functionality as a Task Pane, Content Agave and Contextual Agave. Agaves are available for Word, Excel and Outlook; however, Outlook requires Exchange 2013. Agaves are like SharePoint apps, but they integrate external content with that functionality within Office APIs in the Task Pane, as well as the content. Each Agave works differently so you will need to check the functionality available for each of them.
Check back next week when we explore what SharePoint 2013 holds in store for Designers.
Editor's Note: To read what SharePoint 2013 has in store for Administrators:
About the Author
Brian Alderman earned a Master's Degree in Computer Information Systems. Since 1995, Alderman has earned several Microsoft certifications that currently include MCT, MCITP for SharePoint, MCITP for SQL ServerŪ, MCSA and MCSE for Windows ServerŪ, and also a PMP certification. For more information, visit www.mindsharp.com or follow Alderman @brianalderman.
- Has Google Delivered a Killer Blow to Microsoft Office Apps?
- Should You Use LinkedIn to Build a Network or an Audience?
- 5 Marketing Lessons From HubSpot
- Microsoft Leaves Ballmer Bleeding as It Moves On
- A Graceful Exit for Box?
- Dave Gray on Work Like a Network and the Role of Hierarchies
- Does Jive Do Social Better by Putting the End User First?