Skip to content

Commit 78e17d0

Browse files
authored
Updated YAML, intro, and bookmarks
1 parent 3993b7c commit 78e17d0

File tree

1 file changed

+7
-12
lines changed

1 file changed

+7
-12
lines changed

docs/sp-add-ins/get-started-creating-provider-hosted-sharepoint-add-ins.md

Lines changed: 7 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,13 @@
11
---
22
title: Get started creating provider-hosted SharePoint Add-ins
3-
ms.date: 10/30/2017
3+
description: Set up a development environment and create your first provider-hosted SharePoint Add-in.
4+
ms.date: 11/02/2017
45
ms.prod: sharepoint
56
---
67

78

89
# Get started creating provider-hosted SharePoint Add-ins
910

10-
Set up a development environment and create your first provider-hosted SharePoint Add-in.
11-
12-
> [!NOTE]
13-
> 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." For details, see [New name for apps for SharePoint](new-name-for-apps-for-sharepoint.md).
14-
1511
Provider-hosted add-ins are one of the two major types of SharePoint Add-ins. For an overview of SharePoint Add-ins and the two different types, see [SharePoint Add-ins](sharepoint-add-ins.md).
1612

1713
Here's a summary of provider-hosted add-ins:
@@ -25,9 +21,9 @@ Here's a summary of provider-hosted add-ins:
2521
- Step 2 - Create the app project
2622

2723
- Step 3 - Code your app
28-
29-
## Set up your dev environment
24+
3025
<a name="Setup"> </a>
26+
## Set up your dev environment
3127

3228
There are many ways to set up a development environment for SharePoint Add-ins. This section explains the simplest way. For alternatives, see [Additional resources](#bk_addresources).
3329

@@ -37,8 +33,8 @@ There are many ways to set up a development environment for SharePoint Add-ins.
3733

3834
- Visual Studio includes the **Microsoft Office Developer Tools for Visual Studio**. Sometimes a version of the tools is released between updates of Visual Studio. To be sure that you have the latest version of the tools, run the [installer for Office Developer Tools for Visual Studio 2013](http://aka.ms/OfficeDevToolsForVS2013), or the [installer for Office Developer Tools for Visual Studio 2015](http://aka.ms/OfficeDevToolsForVS2015).
3935

40-
### Sign up for an Office 365 Developer Site
4136
<a name="o365_signup"> </a>
37+
### Sign up for an Office 365 Developer Site
4238

4339
> [!NOTE]
4440
> You might already have access to an Office 365 Developer Site:
@@ -91,9 +87,8 @@ There are three ways to get an Office 365 plan:
9187

9288
![Screenshot that shows the Developer site homepage.](../images/SP15_DeveloperSiteHome_border.png)
9389

94-
95-
## Create the add-in project
9690
<a name="Create"> </a>
91+
## Create the add-in project
9792

9893
1. Start Visual Studio by using the **Run as administrator** option.
9994

@@ -121,8 +116,8 @@ There are three ways to get an Office 365 plan:
121116

122117
Much of the configuration is done when the solution opens. Two projects are created in the Visual Studio solution: one for the SharePoint Add-in and the other for the ASP.NET web application.
123118

124-
## Code your add-in
125119
<a name="Code"> </a>
120+
## Code your add-in
126121

127122
1. Open the AppManifest.xml file. On the **Permissions** tab, specify the **Site Collection** scope and the **Read** permission level.
128123

0 commit comments

Comments
 (0)