DEPLOYING AN APP
The options available for deploying apps depend on your deployment scenario and application type. There are three main application types and each one requires a different deployment scenario. Table 7-1 summarizes these various scenarios.
TABLE 7-1: Application Deployment Summary
| APP TYPE | APP CODE DEPLOYED TO | APP PACKAGE DEPLOYED TO |
| SharePoint-hosted | N/A | App catalog or Marketplace |
| Provider-hosted | Azure or other | App catalog or Marketplace |
| Autohosted | Azure | App catalog or Marketplace |
SharePoint-hosted apps are a bit simpler than the others given that there isn’t any Web deploy package to have deployed, and because they generally consist of HTML pages and JavaScript only. SharePoint-hosted apps don’t have any other dependencies on a runtime environment for this reason.
Provider-hosted apps are a bit more complex and consist of just an app package without any Web deploy package in it. This is because the provider of the app is already required to be hosting it either in Azure or some other Internet-accessible location. The provider of the app manages running the code for the app and any associated databases or dependent resources.
Autohosted app packages are the only ones that contain Web deploy packages and/or database packages. This is because Autohosted apps are the only app types where SharePoint needs to take both the Web deploy package and database package and deploy them to Azure when the app is installed. Azure is currently the only option for autodeployment ...
Get Beginning SharePoint 2013 Development now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
