This project is read-only.


 To build and deploy autohosted / SharePoint-hosted apps for SharePoint:

  1. Check in the foldrs and the files from the project into the root of your source control team project. Your source control project folder structure should look like the following after check-in: 
  2. Update Parameters.ps1 as needed to specify your SharePoint URL and the account. Check the file into source control after modification.
  3. Create a new build definition using OfficeToolsAppTemplate.xaml.
  4. Go to the Process tab of the build definition, expand the Misc category in “Build process parameters”, and then select SharePointAppDeploy.ps1 as the deployment script for this build template:
  5. Save the build definition, and you are ready to go.

Note: After an autohosted / SharePoint-hosted app is deployed, you’ll have to go to the app info page and trust it before you can successfully navigate to the app page. 

To build provider-hosted apps for SharePoint or apps for Office:

  1. Follow these instructions to configure your build agent so that TFS build server can remotely deploy the web application in the SharePoint project to your web server.
  2. In your provider-hosted app for SharePoint project, right-click the project in Solution Explorer and select Publish command. After following the instructions in the Publish wizard, a publish profile (.pubxml) is generated in your web project after you finish all the steps in the wizard. Check that profile file into your source control team project.
  3. Follow all the steps in the section “To build and deploy autohosted / SharePoint-hosted apps for SharePoint” above to create the proper layout of your team project and the build definition. For apps for Office, use the following scripts as the deployment script in the build template:
    1. Content / task pane apps: ContentAndTaskPaneDeploy.ps1
    2. Mail apps: MailAppDeploy.ps1
  4. In the build definition, update the MSBuildArguments parameter (under Advanced category) to /p:ActivePublishProfile=”<YourPublishProfileName>”, and then save the build definition:
  5. Save the build definition and you are ready to go.

 To build SharePoint Farm / Sandboxed solutions:


  • If you are using TFS Online, the target SharePoint / Web site for deployment needs to be public accessible.

Other Resources:

Last edited Mar 20, 2013 at 5:14 AM by XiaoyingGuo, version 25


No comments yet.