Skip to content

Commit

Permalink
Merge pull request MicrosoftDocs#23369 from tdykstra/0420a
Browse files Browse the repository at this point in the history
clarifications and rorder prereqs
  • Loading branch information
ggailey777 committed Apr 20, 2016
2 parents 728e3db + 3c418c1 commit 665131a
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 11 deletions.
16 changes: 9 additions & 7 deletions articles/app-service-api/app-service-api-dotnet-get-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ In this section, you verify that you can run the client locally and can call the

c. Set **Action** to **Start** for each project.

2. Press F5 to start the projects.
2. Press F5 or click **Debug > Start Debugging** to start the projects in debug mode.

Three browser windows open. Two browser windows show HTTP 403 error pages (directory browsing not allowed), which is normal for Web API projects. The third browser window shows the AngularJS UI.

Expand All @@ -113,9 +113,9 @@ An ASP.NET Web API project can dynamically generate Swagger metadata by using th

In this section of the tutorial, you look at the generated Swagger 2.0 metadata, and then you try out a test UI that is based on the Swagger metadata.

2. Set the ToDoListDataAPI project as the startup project.
2. Set the ToDoListDataAPI project (**not** the ToDoListAPI project) as the startup project.

4. Press F5 to run the project in debug mode.
4. Press F5 or click **Debug > Start Debugging** to run the project in debug mode.

The browser opens and shows the HTTP 403 error page.

Expand Down Expand Up @@ -190,7 +190,7 @@ In this section of the tutorial, you look at the generated Swagger 2.0 metadata,

![Swagger UI available methods](./media/app-service-api-dotnet-get-started/methods.png)

5. Click **Get**.
5. Click the first **Get** button in the list.

6. Enter an asterisk as the value of the `owner` parameter, and then click **Try it out**.

Expand Down Expand Up @@ -220,11 +220,11 @@ In this section of the tutorial, you look at the generated Swagger 2.0 metadata,

The ToDoList API returns an HTTP 204 response code that indicates success.

11. Click **Get > Try it out**.
11. Click the first **Get** button, and then in that section of the page click the **Try it out** button.

The Get method response now includes the new to do item.

12. Try also the Put, Delete, and Get by ID methods.
12. Optional: Try also the Put, Delete, and Get by ID methods.

14. Close the browser and stop Visual Studio debugging.

Expand Down Expand Up @@ -470,7 +470,7 @@ If you called the middle tier API app now, it would try to call the data tier us

1. Go to the [Azure portal](https://portal.azure.com/), and then navigate to the **API App** blade for the API app that you created to host the TodoListAPI (middle tier) project.

2. In the API App's **Settings** blade, click **App settings**.
2. In the API App's **Settings** blade, click **Application settings**.

4. In the API App's **Application Settings** blade, scroll down to the **App settings** section and add the following key and value:

Expand Down Expand Up @@ -521,6 +521,8 @@ For an example of an Azure Resource Manager template that sets the API definitio

If you run into a problem as you go through this tutorial, make sure that you're using the latest version of the Azure SDK for .NET. The easiest way to do that is to [download the Azure SDK for Visual Studio 2015](http://go.microsoft.com/fwlink/?linkid=518003) -- if you have the current version installed, the Web Platform Installer lets you know that no installation is needed.

Two of the project names are similar (ToDoListAPI, ToDoListDataAPI). If things don't look as described in the instructions when you are working with a project, make sure you have opened the correct project.

If you're on a corporate network and are trying to deploy to Azure App Service through a firewall, make sure that ports 443 and 8172 are open for Web Deploy. If you can't open those ports, see the following Next steps section for other deployment options.

If you accidentally deploy the wrong project to an API app and then later deploy the correct one to it, you might see "Route names must be unique" errors. To correct this, redeploy the project to the API app, and on the **Settings** tab of the **Publish Web** wizard select **Remove additional files at destination**.
Expand Down
8 changes: 4 additions & 4 deletions includes/app-service-api-dotnet-get-started-prereqs.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,7 @@
### ASP.NET Web API

The tutorial assumes that you have a basic knowledge of how to work with ASP.NET [Web API 2](http://www.asp.net/web-api/overview/getting-started-with-aspnet-web-api/tutorial-your-first-web-api) in Visual Studio.

### Azure account

You need an Azure account to complete the tutorial. You can:
Expand All @@ -14,7 +18,3 @@ The tutorial is written for Visual Studio 2015 with the Azure SDK for .NET 2.8.2
If you have Visual Studio 2013, and you want to use that, [download the latest Azure SDK for Visual Studio 2013](http://go.microsoft.com/fwlink/?LinkID=324322). The instructions are basically the same but some screens may look different.

>[AZURE.NOTE] Depending on how many of the SDK dependencies you already have on your machine, installing the SDK could take a long time, from several minutes to a half hour or more.
### ASP.NET Web API

The tutorial assumes that you have a basic knowledge of how to work with ASP.NET [Web API 2](http://www.asp.net/web-api/overview/getting-started-with-aspnet-web-api/tutorial-your-first-web-api) in Visual Studio.

0 comments on commit 665131a

Please sign in to comment.