Adding peer edit feedback.

Author: TimShererWithAquent

articles/service-bus-relay/media/service-bus-dotnet-hybrid-app-using-service-bus-relay/run-web-app-locally-no-content.png

@@ -19,22 +19,23 @@ ms.author: spelluru
 ---
 # Expose an on-premises WCF service to a web application in the cloud by using Azure Relay
 
-This article shows how to build a hybrid cloud application with Microsoft Azure and Visual Studio. You create an application that uses multiple Azure resources up and running in the cloud.
+This article shows how to build a hybrid cloud application with Microsoft Azure and Visual Studio. You create an application that uses multiple Azure resources in the cloud. This tutorial helps you learn:
 
 * How to create or adapt an existing web service for consumption by a web solution.
 * How to use the Azure Windows Communication Foundation (WCF) Relay service to share data between an Azure application and a web service hosted elsewhere.
 
-You take the following steps in this tutorial:
+You do the following tasks in this tutorial:
 
 > [!div class="checklist"]
 >
+> * Install prerequisites for this tutorial.
 > * Review the scenario.
 > * Create a namespace.
-> * Create an on-premises server
-> * Create an ASP .NET application
+> * Create an on-premises server.
+> * Create an ASP .NET application.
 > * Run the app locally.
-> * Deploy the web app to Azure
-> * Run the app on Azure
+> * Deploy the web app to Azure.
+> * Run the app on Azure.
 
 ## Prerequisites
 
@@ -46,42 +47,40 @@ To complete this tutorial, you need the following prerequisites:
 
 ## How Azure Relay helps with hybrid solutions
 
-Business solutions are typically composed of a combination of custom code and existing functionality. Custom code tackles new and unique business requirements. Existing functionality is provided by solutions and systems that are already in place.
+Business solutions are typically composed of a combination of custom code and existing functionality. Custom code tackles new and unique business requirements. Solutions and systems that are already in place provide existing functionality.
 
-Solution architects are starting to use the cloud for easier handling of scale requirements and lower operational costs. In doing so, they find that existing service assets they'd like to use as building blocks for their solutions are inside the corporate firewall and out of easy reach for access by the cloud solution. Many internal services aren't built or hosted in a way that they can be easily exposed at the corporate network edge.
+Solution architects are starting to use the cloud for easier handling of scale requirements and lower operational costs. In doing so, they find that existing service assets they'd like to use as building blocks for their solutions are inside the corporate firewall and out of easy reach by the cloud solution. Many internal services aren't built or hosted in a way that they can be easily exposed at the corporate network edge.
 
-[Azure Relay](https://azure.microsoft.com/services/service-bus/) is designed for the use-case of taking existing WCF web services and making those services securely accessible to solutions that are outside the corporate perimeter without requiring intrusive changes to the corporate network infrastructure. Such relay services are still hosted inside their existing environment, but they delegate listening for incoming sessions and requests to the cloud-hosted relay service. Azure Relay also protects those services from unauthorized access by using [Shared Access Signature (SAS)](../service-bus-messaging/service-bus-sas.md) authentication.
+[Azure Relay](https://azure.microsoft.com/services/service-bus/) takes existing WCF web services and makes those services securely accessible to solutions that are outside the corporate perimeter without requiring intrusive changes to the corporate network infrastructure. Such relay services are still hosted inside their existing environment, but they delegate listening for incoming sessions and requests to the cloud-hosted relay service. Azure Relay also protects those services from unauthorized access by using [Shared Access Signature (SAS)](../service-bus-messaging/service-bus-sas.md) authentication.
 
 ## Review the scenario
 
 In this tutorial, you create an ASP.NET website that enables you to see a list of products on the product inventory page.
 
 ![Scenario][0]
 
-The tutorial assumes that you have product information in an existing on-premises system, and uses Azure Relay to reach into that system. This situation is simulated by a web service that runs in a simple console application and is backed by an in-memory set of products. You can run this console application on your own computer and deploy the web role into Azure. By doing so, you'll see how the web role running in the Azure datacenter calls into your computer. This call happens even though your computer will almost certainly be behind at least one firewall and a network address translation (NAT) layer.
+The tutorial assumes that you have product information in an existing on-premises system, and uses Azure Relay to reach into that system. A web service that runs in a simple console application simulates this situation. It contains an in-memory set of products. You can run this console application on your own computer and deploy the web role into Azure. By doing so, you'll see how the web role running in the Azure datacenter calls into your computer. This call happens even though your computer will almost certainly be behind at least one firewall and a network address translation (NAT) layer.
 
 ## Set up the development environment
 
 Before you can begin developing Azure applications, download the tools and set up your development environment:
 
 1. Install the Azure SDK for .NET from the SDK [downloads page](https://azure.microsoft.com/downloads/).
 1. In the **.NET** column, choose the version of [Visual Studio](https://www.visualstudio.com) you're using. This tutorial uses Visual Studio 2019.
-1. When prompted to run or save the installer, Select **Run**.
-1. In the **Web Platform Installer**, select **Install** and continue with the installation.
+1. When prompted to run or save the installer, select **Run**.
+1. In the **Web Platform Installer** dialog box, select **Install** and continue with the installation.
 
-Once the installation is complete, you have everything necessary to start to develop the app. The SDK includes tools that let you easily develop Azure applications in Visual Studio.
+Once the installation is finished, you have everything necessary to start to develop the app. The SDK includes tools that let you easily develop Azure applications in Visual Studio.
 
 ## Create a namespace
 
-The first step is to create a namespace, and to obtain a [Shared Access Signature (SAS)](../service-bus-messaging/service-bus-sas.md) key. A namespace provides an application boundary for each application exposed through the relay service. A SAS key is automatically generated by the system when a service namespace is created. The combination of service namespace and SAS key provides the credentials for Azure to authenticate access to an application.
+The first step is to create a namespace, and to obtain a [Shared Access Signature (SAS)](../service-bus-messaging/service-bus-sas.md) key. A namespace provides an application boundary for each application exposed through the relay service. An SAS key is automatically generated by the system when a service namespace is created. The combination of service namespace and SAS key provides the credentials for Azure to authenticate access to an application.
 
 [!INCLUDE [relay-create-namespace-portal](../../includes/relay-create-namespace-portal.md)]
 
 ## Create an on-premises server
 
-First, you build a simulated on-premises product catalog system.  This project is a Visual Studio console application, and uses the [Azure Service Bus NuGet package](https://www.nuget.org/packages/WindowsAzure.ServiceBus/) to include the Service Bus libraries and configuration settings.
-
-### Create the project
+First, you build a simulated on-premises product catalog system.  This project is a Visual Studio console application, and uses the [Azure Service Bus NuGet package](https://www.nuget.org/packages/WindowsAzure.ServiceBus/) to include the Service Bus libraries and configuration settings. <a name="create-the-project"></a>
 
 1. Start Microsoft Visual Studio as an administrator. To do so, right-click the Visual Studio program icon, and select **Run as administrator**.
 1. In Visual Studio, select **Create a new project**.
@@ -99,6 +98,9 @@ First, you build a simulated on-premises product catalog system.  This project i
 
 1. Add a new class for your product contract. In **Solution Explorer**, right-click the **ProductsServer** project and select **Add** > **Class**.
 1. In **Name**, enter the name *ProductsContract.cs* and select **Add**.
+
+Make the following code changes to your solution:
+
 1. In *ProductsContract.cs*, replace the namespace definition with the following code, which defines the contract for the service.
 
     ```csharp
@@ -228,7 +230,7 @@ First, you build a simulated on-premises product catalog system.  This project i
     </appSettings>
     ```
 
-1. Press Ctrl+Shift+B or select **Build** > **Build Solution** to build the application and verify the accuracy of your work so far.
+1. Select Ctrl+Shift+B or select **Build** > **Build Solution** to build the application and verify the accuracy of your work so far.
 
 ## Create an ASP.NET application
 
@@ -249,7 +251,7 @@ In this section, you build a simple ASP.NET application that displays data retri
     ![Specify authentication][18]
 
 1. Back in **Create a new ASP.NET Web Application**, select **Create** to create the MVC app.
-1. Configure Azure resources for a new web app. Follow the steps in the [Publish to Azure section of this article](../app-service/app-service-web-get-started-dotnet-framework.md#launch-the-publish-wizard). Then, return to this tutorial and continue to the next step.
+1. Configure Azure resources for a new web app. Follow the steps in [Publish your web app](../app-service/app-service-web-get-started-dotnet-framework.md#launch-the-publish-wizard). Then, return to this tutorial and continue to the next step.
 1. In **Solution Explorer**, right-click **Models** and then select **Add** > **Class**.
 1. Name the class *Product.cs*, then select **Add**.
 
@@ -337,14 +339,14 @@ In this section, you build a simple ASP.NET application that displays data retri
    </table>
    ```
 
-1. To verify the accuracy of your work so far, you can press Ctrl+Shift+B to build the project.
+1. To verify the accuracy of your work so far, you can select Ctrl+Shift+B to build the project.
 
 ### Run the app locally
 
 Run the application to verify that it works.
 
 1. Ensure that **ProductsPortal** is the active project. Right-click the project name in **Solution Explorer** and select **Set As Startup Project**.
-1. In Visual Studio, press **F5**.
+1. In Visual Studio, select F5.
 
 Your application should appear, running in a browser.
 
@@ -355,14 +357,14 @@ Your application should appear, running in a browser.
 The next step is to hook up the on-premises products server with the ASP.NET application.
 
 1. If it isn't already open, in Visual Studio, open the **ProductsPortal** project you created in the [Create an ASP.NET application](#create-an-aspnet-application) section.
-1. Similar to the step in the [Create an On-Premises Server](#create-an-on-premises-server) section, add the NuGet package to the project references. In **Solution Explorer**, right-click the **ProductsPortal** project, then select **Manage NuGet Packages**.
-1. Search for *WindowsAzure.ServiceBus* and select the **WindowsAzure.ServiceBus** item. Then complete the installation and close this dialog box.
+1. Similar to the step in the [Create an on-premises server](#create-an-on-premises-server) section, add the NuGet package to the project references. In **Solution Explorer**, right-click the **ProductsPortal** project, then select **Manage NuGet Packages**.
+1. Search for *WindowsAzure.ServiceBus* and select the **WindowsAzure.ServiceBus** item. Then finish the installation and close this dialog box.
 1. In **Solution Explorer**, right-click the **ProductsPortal** project, then select **Add** > **Existing Item**.
 1. Navigate to the *ProductsContract.cs* file from the **ProductsServer** console project. Highlight *ProductsContract.cs*. Select the down arrow next to **Add**, then choose **Add as Link**.
 
    ![Add as a link][24]
 
-1. Now open the *HomeController.cs* file in the Visual Studio editor and replace the namespace definition with the following code. Be sure to replace `yourServiceNamespace` with the name of your service namespace, and `yourKey` with your SAS key. This code enables the client to call the on-premises service, returning the result of the call.
+1. Now open the *HomeController.cs* file in the Visual Studio editor and replace the namespace definition with the following code. Be sure to replace `yourServiceNamespace` with the name of your service namespace, and `yourKey` with your SAS key. This code lets the client to call the on-premises service, returning the result of the call.
 
    ```csharp
    namespace ProductsWeb.Controllers
@@ -412,20 +414,19 @@ The next step is to hook up the on-premises products server with the ASP.NET app
       ![Multiple startup projects][25]
 
 1. Select **Common Properties** > **Project Dependencies** on the left side.
-1. For **Projects**, choose **ProductsServer**. Ensure that **ProductsPortal** isn't selected.
 1. For **Projects**, choose **ProductsPortal**. Ensure that **ProductsServer** is selected.
 
     ![Project dependencies][26]
 
-1. Select **OK** to save your changes.
+1. For **Projects**, choose **ProductsServer**. Ensure that **ProductsPortal** isn't selected, and then select **OK** to save your changes.
 
 ## Run the project locally
 
-To test the application locally, in Visual Studio press **F5**. The on-premises server, **ProductsServer**, should start first, then the **ProductsPortal** application should start in a browser window. This time, you see that the product inventory lists data retrieved from the product service on-premises system.
+To test the application locally, in Visual Studio select F5. The on-premises server, **ProductsServer**, should start first, then the **ProductsPortal** application should start in a browser window. This time, you see that the product inventory lists data retrieved from the product service on-premises system.
 
 ![Web application][10]
 
-Press **Refresh** on the **ProductsPortal** page. Each time you refresh the page, you see the server app display a message when `GetProducts()` from **ProductsServer** is called.
+Select **Refresh** on the **ProductsPortal** page. Each time you refresh the page, you see the server app display a message when `GetProducts()` from **ProductsServer** is called.
 
 Close both applications before proceeding to the next section.
 
@@ -439,15 +440,13 @@ The next step is to republish the Azure Web app **ProductsPortal** front end:
    > You may see an error message in the browser window when the **ProductsPortal** web project is automatically launched after the deployment. This is expected, and occurs because the **ProductsServer** application isn't running yet.
    >
 
-1. Copy the URL of the deployed web app. You'll need the URL later. You can also obtain this URL from the **Azure App Service Activity** window in Visual Studio:
+1. Copy the URL of the deployed web app. You'll need the URL later. You can also get this URL from the **Azure App Service Activity** window in Visual Studio:
 
    ![URL of the deployed app][9]
 
 1. Close the browser window to stop the running application.
 
-### Set ProductsPortal as web app
-
-Before running the application in the cloud, you must ensure that **ProductsPortal** is launched from within Visual Studio as a web app.
+<a name="set-productsportal-as-web-app"></a>Before running the application in the cloud, you must ensure that **ProductsPortal** is launched from within Visual Studio as a web app.
 
 1. In Visual Studio, right-click the **ProductsPortal** project and select **Properties**.
 1. Select **Web**. Under **Start Action**, choose **Start URL**. Enter the URL for your previously deployed web app, in this example, `https://productsportal20190906122808.azurewebsites.net/`.
@@ -459,19 +458,19 @@ Before running the application in the cloud, you must ensure that **ProductsPort
 
 ## Run the application
 
-Press **F5** to build and run the application. The on-premises server, which is the **ProductsServer** console application, should start first, then the **ProductsPortal** application should start in a browser window, as shown here:
+Select F5 to build and run the application. The on-premises server, which is the **ProductsServer** console application, should start first, then the **ProductsPortal** application should start in a browser window, as shown here:
 
    ![Run the web app on Azure][1]
 
 The product inventory lists data retrieved from the product service on-premises system, and displays that data in the web app. Check the URL to make sure that **ProductsPortal** is running in the cloud, as an Azure web app.
 
    > [!IMPORTANT]
-   > The **ProductsServer** console application must be running and able to serve the data to the **ProductsPortal** application. If the browser displays an error, wait a few more seconds for **ProductsServer** to load and display the following message. Then press **Refresh** in the browser.
+   > The **ProductsServer** console application must be running and able to serve the data to the **ProductsPortal** application. If the browser displays an error, wait a few more seconds for **ProductsServer** to load and display the following message, then refresh the browser.
    >
 
-In the browser, press **Refresh** on the **ProductsPortal** page. Each time you refresh the page, you see the server app display a message when `GetProducts()` from **ProductsServer** is called.
+In the browser, refresh the **ProductsPortal** page. Each time you refresh the page, you see the server app display a message when `GetProducts()` from **ProductsServer** is called.
 
-    ![Updated output][38]
+![Updated output][38]
 
 ## Next steps
 
@@ -493,7 +492,7 @@ Advance to the following tutorial:
 [9]: ./media/service-bus-dotnet-hybrid-app-using-service-bus-relay/web-publish-activity.png
 [10]: ./media/service-bus-dotnet-hybrid-app-using-service-bus-relay/run-web-app-locally.png
 
-[21]: ./media/service-bus-dotnet-hybrid-app-using-service-bus-relay/App1.png
+[21]: ./media/service-bus-dotnet-hybrid-app-using-service-bus-relay/run-web-app-locally-no-content.png
 [24]: ./media/service-bus-dotnet-hybrid-app-using-service-bus-relay/add-existing-item-link.png
 [25]: ./media/service-bus-dotnet-hybrid-app-using-service-bus-relay/hy-web-13.png
 [26]: ./media/service-bus-dotnet-hybrid-app-using-service-bus-relay/hy-web-14.png