Merge pull request #83624 from TimShererWithAquent/us1546060b

Freshness pass, various edits, per 1546060

Author: Jak-MS

articles/iot-hub/iot-hub-csharp-csharp-module-twin-getstarted.md

@@ -6,7 +6,7 @@ ms.service: iot-hub
 services: iot-hub
 ms.devlang: csharp
 ms.topic: conceptual
-ms.date: 04/26/2018
+ms.date: 08/07/2019
 ms.author: menchi
 ---
 
@@ -15,24 +15,24 @@ ms.author: menchi
 [!INCLUDE [iot-hub-selector-module-twin-getstarted](../../includes/iot-hub-selector-module-twin-getstarted.md)]
 
 > [!NOTE]
-> [Module identities and module twins](iot-hub-devguide-module-twins.md) are similar to Azure IoT Hub device identity and device twin, but provide finer granularity. While Azure IoT Hub device identity and device twin enable the back-end application to configure a device and provides visibility on the device’s conditions, a module identity and module twin provide these capabilities for individual components of a device. On capable devices with multiple components, such as operating system based devices or firmware devices, it allows for isolated configuration and conditions for each component.
+> [Module identities and module twins](iot-hub-devguide-module-twins.md) are similar to Azure IoT Hub device identity and device twin, but provide finer granularity. While Azure IoT Hub device identity and device twin enable the back-end application to configure a device and provide visibility on the device’s conditions, a module identity and module twin provide these capabilities for individual components of a device. On capable devices with multiple components, such as operating system based devices or firmware devices, module identities and module twins allow for isolated configuration and conditions for each component.
 
 At the end of this tutorial, you have two .NET console apps:
 
-* **CreateIdentities**, which creates a device identity, a module identity and associated security key to connect your device and module clients.
+* **CreateIdentities**. This app creates a device identity, a module identity, and associated security key to connect your device and module clients.
 
-* **UpdateModuleTwinReportedProperties**, which sends updated module twin reported properties to your IoT Hub.
+* **UpdateModuleTwinReportedProperties**. This app sends updated module twin reported properties to your IoT hub.
 
 > [!NOTE]
 > For information about the Azure IoT SDKs that you can use to build both applications to run on devices, and your solution back end, see [Azure IoT SDKs](iot-hub-devguide-sdks.md).
 
-To complete this tutorial, you need the following:
+To complete this tutorial, you need the following prerequisites:
 
 * Visual Studio.
 
-* An active Azure account. (If you don't have an account, you can create a [free account](https://azure.microsoft.com/pricing/free-trial/) in just a couple of minutes.)
+* An active Azure account. If you don't have an account, you can create a [free account](https://azure.microsoft.com/pricing/free-trial/) in just a couple of minutes.
 
-## Create an IoT hub
+## Create a hub
 
 [!INCLUDE [iot-hub-include-create-hub](../../includes/iot-hub-include-create-hub.md)]
 
@@ -48,21 +48,25 @@ To complete this tutorial, you need the following:
 
 In this section, you create a .NET console app on your simulated device that updates the module twin reported properties.
 
-1. **Create a Visual Studio project:** In Visual Studio, add a Visual C# Windows Classic Desktop project to the existing solution by using the **Console App (.NET Framework)** project template. Make sure the .NET Framework version is 4.6.1 or later. Name the project **UpdateModuleTwinReportedProperties**.
+Before you begin, get your module connection string. Sign in to the [Azure portal](https://portal.azure.com/). Navigate to your hub and select **IoT Devices**. Find **myFirstDevice**. Select **myFirstDevice** to open it, and then select **myFirstModule** to open it. In **Module Identity Details**, copy the **Connection string (primary key)** when needed in the following procedure.
 
-    ![Create a visual studio project](./media/iot-hub-csharp-csharp-module-twin-getstarted/update-twins-csharp1.png)
+   ![Azure portal module detail](./media/iot-hub-csharp-csharp-module-twin-getstarted/module-identity-detail.png)
 
-2. **Install the latest Azure IoT Hub .NET device SDK:** Module identity and module twin is in public preview. It's only available in the IoT Hub prerelease device SDKs. In Visual Studio, open tools > Nuget package manager > manage Nuget packages for solution. Search Microsoft.Azure.Devices.Client. Make sure you've checked include prerelease check box. Select the latest version and install. Now you have access to all the module features. 
+1. In Visual Studio, add a new project to your solution by selecting **File** > **New** > **Project**. In Create a new project, select **Console App (.NET Framework)**, and select **Next**.
 
-    ![Install Azure IoT Hub .NET service SDK V1.16.0-preview-005](./media/iot-hub-csharp-csharp-module-twin-getstarted/install-sdk.png)
+1. Name the project *UpdateModuleTwinReportedProperties*. For **Solution**, select **Add to solution**. Make sure the .NET Framework version is 4.6.1 or later.
 
-3. **Get your module connection string** -- now if you sign in to [Azure portal](https://portal.azure.com/). Navigate to your IoT Hub and click IoT Devices. Find myFirstDevice, open it and you see myFirstModule was successfully created. Copy the module connection string. It is needed in the next step.
+    ![Create a Visual Studio project](./media/iot-hub-csharp-csharp-module-twin-getstarted/configure-update-twins-csharp1.png)
 
-    ![Azure portal module detail](./media/iot-hub-csharp-csharp-module-twin-getstarted/module-detail.png)
+1. Select **Create** to create your project.
 
-4. **Create UpdateModuleTwinReportedProperties console app**
+1. In Visual Studio, open **Tools** > **NuGet Package Manager** > **Manage NuGet Packages for Solution**. Select the **Browse** tab.
 
-    Add the following `using` statements at the top of the **Program.cs** file:
+1. Search for and select **Microsoft.Azure.Devices.Client**, and then select **Install**.
+
+    ![Install Azure IoT Hub .NET service SDK current version](./media/iot-hub-csharp-csharp-module-twin-getstarted/install-client-sdk.png)
+
+1. Add the following `using` statements at the top of the **Program.cs** file:
 
     ```csharp
     using Microsoft.Azure.Devices.Client;
@@ -71,11 +75,10 @@ In this section, you create a .NET console app on your simulated device that upd
     using Newtonsoft.Json;
     ```
 
-    Add the following fields to the **Program** class. Replace the placeholder value with the module connection string.
+1. Add the following fields to the **Program** class. Replace the placeholder value with the module connection string.
 
     ```csharp
-    private const string ModuleConnectionString = 
-      "<Your module connection string>";
+    private const string ModuleConnectionString = "<Your module connection string>";
     private static ModuleClient Client = null;
     static void ConnectionStatusChangeHandler(ConnectionStatus status, 
       ConnectionStatusChangeReason reason)
@@ -85,7 +88,7 @@ In this section, you create a .NET console app on your simulated device that upd
     }
     ```
 
-    Add the following method **OnDesiredPropertyChanged** to the **Program** class:
+1. Add the following method **OnDesiredPropertyChanged** to the **Program** class:
 
     ```csharp
     private static async Task OnDesiredPropertyChanged(TwinCollection desiredProperties, 
@@ -103,7 +106,7 @@ In this section, you create a .NET console app on your simulated device that upd
         }
     ```
 
-    Finally, add the following lines to the **Main** method:
+1. Add the following lines to the **Main** method:
 
     ```csharp
     static void Main(string[] args)
@@ -143,7 +146,7 @@ In this section, you create a .NET console app on your simulated device that upd
 
     This code sample shows you how to retrieve the module twin and update reported properties with AMQP protocol. In public preview, we only support AMQP for module twin operations.
 
-5. In addition to the above **Main** method, you can add below code block to send event to IoT Hub from your module:
+1. Optionally, you can add these statements to the **Main** method to send an event to IoT Hub from your module. Place these lines below the `try catch` block.
 
     ```csharp
     Byte[] bytes = new Byte[2];
@@ -156,11 +159,20 @@ In this section, you create a .NET console app on your simulated device that upd
 
 ## Run the apps
 
-You are now ready to run the apps. In Visual Studio, in Solution Explorer, right-click your solution, and then click **Set StartUp projects**. Select **Multiple startup projects**, and then select **Start** as the action for the console app. And then press F5 to start the app.
+You can now run the apps.
+
+1. In Visual Studio, in **Solution Explorer**, right-click your solution, and then select **Set StartUp projects**.
+
+1. Under **Common Properties**, select **Startup Project.**
+
+1. Select **Multiple startup projects**, and then select **Start** as the action for the apps, and **OK** to accept your changes.
+
+1. Press **F5** to start the apps.
 
 ## Next steps
 
 To continue getting started with IoT Hub and to explore other IoT scenarios, see:
 
 * [Getting started with device management](iot-hub-node-node-device-management-get-started.md)
+
 * [Getting started with IoT Edge](../iot-edge/tutorial-simulate-device-linux.md)

articles/iot-hub/media/iot-hub-csharp-csharp-module-twin-getstarted/configure-update-twins-csharp1.png

@@ -5,41 +5,48 @@ services: iot-hub
 author: chrissie926
 ms.service: iot-hub
 ms.topic: include
-ms.date: 04/26/2018
+ms.date: 08/07/2019
 ms.author: menchi
 ms.custom: include file
 ---
 
 ## Create a module identity
 
-In this section, you create a .NET console app that creates a device identity and a module identity in the identity registry in your IoT hub. A device or module cannot connect to IoT hub unless it has an entry in the identity registry. For more information, see the [Identity Registry section of the IoT Hub developer guide](../articles/iot-hub/iot-hub-devguide-identity-registry.md). When you run this console app, it generates a unique ID and key for both device and module. Your device and module use these values to identify itself when it sends device-to-cloud messages to IoT Hub. The IDs are case-sensitive.
+In this section, you create a .NET console app that creates a device identity and a module identity in the identity registry in your hub. A device or module can't connect to hub unless it has an entry in the identity registry. For more information, see the [Identity Registry section of the IoT Hub developer guide](../articles/iot-hub/iot-hub-devguide-identity-registry.md).
 
+When you run this console app, it generates a unique ID and key for both device and module. Your device and module use these values to identify themselves when it sends device-to-cloud messages to IoT Hub. The IDs are case-sensitive.
 
-1. **Create a Visual Studio project** - In Visual Studio, add a Visual C# Windows Classic Desktop project to a new solution by using the **Console App (.NET Framework)** project template. Make sure the .NET Framework version is 4.6.1 or later. Name the project **CreateIdentities** and name the solution **IoTHubGetStarted**.
+1. Open Visual Studio, and select **Create a new project**.
 
-    ![Create a visual studio solution](./media/iot-hub-get-started-create-module-identity-csharp/create-identities-csharp1.JPG)
+1. In **Create a new project**, select **Console App (.NET Framework)**.
 
-2. **Install Azure IoT Hub .NET service SDK V1.16.0-preview-001** - Module identity and module twin is in public preview. It's only available in the IoT Hub prerelease service SDKs. In Visual Studio, open tools > Nuget package manager > manage Nuget packages for solution. Search Microsoft.Azure.Devices. Make sure you've checked include prerelease check box. Select version 1.16.0-preview-001 and install. Now you have access to all the module features. 
+1. Select **Next** to open **Configure your new project**. Name the project *CreateIdentities* and name the solution *IoTHubGetStarted*. Make sure the .NET Framework version is 4.6.1 or later.
 
-    ![Install Azure IoT Hub .NET service SDK V1.16.0-preview-001](./media/iot-hub-get-started-create-module-identity-csharp/install-sdk.png)
+    ![Enter name and framework for your Visual Studio solution](./media/iot-hub-get-started-create-module-identity-csharp/configure-createidentities-project.png)
 
-3. Add the following `using` statements at the top of the **Program.cs** file:
+1. In Visual Studio, open **Tools** > **NuGet Package Manager** > **Manage NuGet Packages for Solution**. Select the **Browse** tab.
+
+1. Search for **Microsoft.Azure.Devices**. Select it and then select **Install**.
+
+    ![Install Azure IoT Hub .NET service SDK current version](./media/iot-hub-get-started-create-module-identity-csharp/install-service-sdk.png)
+
+1. Add the following `using` statements at the top of the **Program.cs** file:
 
    ```csharp
    using Microsoft.Azure.Devices;
    using Microsoft.Azure.Devices.Common.Exceptions;
    ```
 
-4. Add the following fields to the **Program** class. Replace the placeholder value with the IoT Hub connection string for the hub that you created in the previous section.
+1. Add the following fields to the **Program** class. Replace the placeholder value with the IoT Hub connection string for the hub that you created in the previous section.
 
    ```csharp
    const string connectionString = "<replace_with_iothub_connection_string>";
    const string deviceID = "myFirstDevice";
    const string moduleID = "myFirstModule";
    ```
 
-5. Add the following code to the **Main** class.
-   
+1. Add the following code to the **Main** class.
+
    ```csharp
    static void Main(string[] args)
    {
@@ -48,7 +55,7 @@ In this section, you create a .NET console app that creates a device identity an
    }
    ```
 
-6. Add the following methods to the **Program** class:
+1. Add the following methods to the **Program** class:
 
     ```csharp
     private static async Task AddDeviceAsync()
@@ -90,13 +97,13 @@ In this section, you create a .NET console app that creates a device identity an
     }
     ```
 
-    The AddDeviceAsync() method creates a device identity with ID **myFirstDevice**. (If that device ID already exists in the identity registry, the code simply retrieves the existing device information.) The app then displays the primary key for that identity. You use this key in the simulated device app to connect to your IoT hub.
+    The `AddDeviceAsync` method creates a device identity with ID **myFirstDevice**. If that device ID already exists in the identity registry, the code simply retrieves the existing device information. The app then displays the primary key for that identity. You use this key in the simulated device app to connect to your hub.
 
-    The AddModuleAsync() method creates a module identity with ID **myFirstModule** under device **myFirstDevice**. (If that module ID already exists in the identity registry, the code simply retrieves the existing module information.) The app then displays the primary key for that identity. You use this key in the simulated module app to connect to your IoT hub.
+    The `AddModuleAsync` method creates a module identity with ID **myFirstModule** under device **myFirstDevice**. If that module ID already exists in the identity registry, the code simply retrieves the existing module information. The app then displays the primary key for that identity. You use this key in the simulated module app to connect to your hub.
 
    [!INCLUDE [iot-hub-pii-note-naming-device](iot-hub-pii-note-naming-device.md)]
 
-7. Run this application, and make a note of the device key and module key.
+1. Run this app, and make a note of the device key and module key.
 
 > [!NOTE]
-> The IoT Hub identity registry only stores device and module identities to enable secure access to the IoT hub. The identity registry stores device IDs and keys to use as security credentials. The identity registry also stores an enabled/disabled flag for each device that you can use to disable access for that device. If your application needs to store other device-specific metadata, it should use an application-specific store. There is no enabled/disabled flag for module identities. For more information, see [IoT Hub developer guide](../articles/iot-hub/iot-hub-devguide-identity-registry.md).
+> The IoT Hub identity registry only stores device and module identities to enable secure access to the hub. The identity registry stores device IDs and keys to use as security credentials. The identity registry also stores an enabled/disabled flag for each device that you can use to disable access for that device. If your app needs to store other device-specific metadata, it should use an application-specific store. There is no enabled/disabled flag for module identities. For more information, see [IoT Hub developer guide](../articles/iot-hub/iot-hub-devguide-identity-registry.md).

articles/iot-hub/media/iot-hub-csharp-csharp-module-twin-getstarted/install-client-sdk.png

@@ -11,4 +11,4 @@ ms.custom: include file
 ---
 <!-- This contains intro text for the "Get an IoT hub connection string" section in the iot-hub-lang-lang-module-twin-getstarted.md files-->
 
-In this article, you create a backend service that adds a device in the identity registry and then adds a module to that device. To perform these operations, your service requires the **registry write** permission. By default, every IoT Hub is created with a shared access policy named **registryReadWrite** that grants this permission.
+In this article, you create a back-end service that adds a device in the identity registry and then adds a module to that device. Your service requires the **registry write** permission. By default, every IoT hub is created with a shared access policy named **registryReadWrite** that grants this permission.

articles/iot-hub/media/iot-hub-csharp-csharp-module-twin-getstarted/module-identity-detail.png

@@ -5,7 +5,7 @@ author: robinsh
 ms.service: iot-hub
 services: iot-hub
 ms.topic: include
-ms.date: 07/17/2019
+ms.date: 08/07/2019
 ms.author: robinsh
 ms.custom: include file
 ---