Package your add-in using Visual Studio to prepare for publishing
Your Office Add-in package contains an XML manifest file that you'll use to publish the add-in. You'll have to publish the web application files of your project separately. This article describes how to deploy your web project and package your add-in by using Visual Studio 2015.
To deploy your web project using Visual Studio 2015
Complete the following steps to deploy your web project using Visual Studio 2015.
In Solution Explorer, open the shortcut menu for the add-in project, and then choose Publish.
The Publish your add-in page appears.
In the Current profile drop-down list, select a profile or choose New ... to create a new profile.
A publish profile specifies the server you are deploying to, the credentials needed to log on to the server, the databases to deploy, and other deployment options.
If you choose New ..., the Create publishing profile wizard appears. You can use this wizard to import a publishing profile from a web site hosting provider such as Microsoft Azure or create a new profile and add your server, credentials, and other settings in the next procedure.
For more information about importing publishing profiles or creating new publishing profiles, see Creating a Publish Profile.
In the Publish your add-in page, choose the Deploy your web project link.
The Publish Web dialog box appears. For more information about using this wizard, see How to: Deploy a Web Project using On-Click Publishing in Visual Studio.
To package your add-in using Visual Studio 2015
Complete the following steps to package your add-in using Visual Studio 2015.
In the Publish your add-in page, choose the Package the add-in link.
The Publish Office and SharePoint Add-ins wizard appears.
In the Where is your website hosted? dropdown list, select or enter the HTTPS URL of the website that will host the content files of your add-in, and then choose Finish.
You must specify a URL that begins with the HTTPS prefix to complete this wizard. If you want to use an HTTP endpoint for your website, you can open the XML manifest file in a text editor after the package has been created and replace the HTTPS prefix of your website with an HTTP prefix.
While not strictly required in all add-in scenarios, using an HTTPS endpoint for your add-in is strongly recommended. Add-ins that are not SSL-secured (HTTPS) generate unsecure content warnings and errors during use. If you plan to run your add-in in Office Online or publish your add-in to AppSource, it must be SSL-secured. If your add-in accesses external data and services, it should be SSL-secured to protect data in transit. Self-signed certificates can be used for development and testing, so long as the certificate is trusted on the local machine. Azure websites automatically provide an HTTPS endpoint.
Visual Studio generates the files that you need to publish your add-in and then opens the publish output folder.
If you plan to submit your add-in to AppSource, you can choose the Perform a validation check link to identify any issues that will prevent your add-in from being accepted. You should address all issues before you submit your add-in to the store.
You can now upload your XML manifest to the appropriate location to publish your add-in. You can find the XML manifest in
OfficeAppManifests in the
app.publish folder. For example:
%UserProfile%\Documents\Visual Studio 2015\Projects\MyApp\bin\Debug\app.publish\OfficeAppManifests