What's new in Office Developer Tools for Visual Studio 2013
You can develop apps for SharePoint by using the following new features available in the Office Developer Tools for Visual Studio.
Last modified: April 30, 2015
Applies to: apps for SharePoint | Office 365 | SharePoint Add-ins | SharePoint Foundation 2013 | SharePoint Server 2013
The name "apps for SharePoint" is changing to "SharePoint Add-ins". During the transition, the documentation and the UI of some SharePoint products and Visual Studio tools might still use the term "apps for SharePoint".
When creating an app for SharePoint, the tools set the target SharePoint version to be the version of the debugging SharePoint website that you specify in the project creation wizard. The wizard shows which SharePoint version is selected and enables you to override that default. You can also change the target version after creating the project through the SharePoint tab in Project Designer.
The tools now install a NuGet package containing the SharePoint Online Client Side Object Model (SPO-CSOM) into your project, when the target version is SharePoint Online. The tools also add references to the SPO-CSOM assemblies to the project. The tools no longer rely on the SharePoint Online Client Component SDK that is released in the Microsoft Download Center. This makes it easier for you to upgrade the CSOM assemblies in the future by using the NuGet Package Manager in Visual Studio.
You can now use either SAS or ACS connection strings for Microsoft Azure Service Bus to Debug and troubleshoot a remote event receiver in an app for SharePoint.
In this release, the tools always create new apps for Office with a v1.1 manifest instead of v1.0, so that your apps can support the new capabilities in Office web apps and Office 2013 clients. For existing apps for Office that use v1.0 manifest, the tools upgrade the manifest to v1.1 when any new capability is used that requires a v1.1 manifest.