Merge pull request #235847 from PatAltimore/patricka-merge-vs-tutorials

Separate debug and develop IoT Edge articles

Author: JamesJBarnett

articles/iot-edge/.openpublishing.redirection.iot-edge.json

@@ -339,6 +339,11 @@
             "source_path_from_root": "/articles/iot-edge/tutorial-python-module.md",
             "redirect_url": "/azure/iot-edge/tutorial-develop-for-linux",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/how-to-vs-code-develop-module.md",
+            "redirect_url": "/azure/iot-edge/tutorial-develop-for-linux",
+            "redirect_document_id": false
         }
     ]
 }

articles/iot-edge/TOC.yml

@@ -18,11 +18,9 @@
   items:
   - name: Develop modules
     items:
-    - name: Develop with Linux containers
+    - name: Develop modules using VS Code
       href: tutorial-develop-for-linux.md
-    - name: Develop and debug with VS Code
-      href: how-to-vs-code-develop-module.md
-    - name: Develop and debug with Visual Studio
+    - name: Develop modules with Visual Studio
       href: how-to-visual-studio-develop-module.md
   - name: Deploy Azure services as modules
     items:
@@ -129,6 +127,8 @@
           href: how-to-use-create-options.md
         - name: Give modules access to a device's local storage
           href: how-to-access-host-storage-from-module.md
+    - name: Debug modules with VS Code
+      href: debug-module-vs-code.md
   - name: Deploy modules
     items:
     - name: Deploy to individual devices

articles/iot-edge/debug-module-vs-code.md

@@ -32,7 +32,7 @@ This article assumes that you're using Modbus TCP protocol. For more information
 
 If you want to test the Modbus gateway functionality, Microsoft has a sample module that you can use. You can access the module from the Azure Marketplace, [Modbus](https://azuremarketplace.microsoft.com/marketplace/apps/microsoft_iot.edge-modbus?tab=Overview), or with the image URI, `mcr.microsoft.com/azureiotedge/modbus:1.0`.
 
-If you want to create your own module and customize it for your environment, there is an open-source [Azure IoT Edge Modbus module](https://github.com/Azure/iot-edge-modbus) project on GitHub. Follow the guidance in that project to create your own container image. To create a container image, refer to [Develop C# modules in Visual Studio](./how-to-visual-studio-develop-module.md) or [Develop modules in Visual Studio Code](how-to-vs-code-develop-module.md). Those articles provide instructions on creating new modules and publishing container images to a registry.
+If you want to create your own module and customize it for your environment, there is an open-source [Azure IoT Edge Modbus module](https://github.com/Azure/iot-edge-modbus) project on GitHub. Follow the guidance in that project to create your own container image. To create a container image, refer to [Develop C# modules in Visual Studio](./how-to-visual-studio-develop-module.md) or [Develop Azure IoT Edge modules using Visual Studio Code](tutorial-develop-for-linux.md). Those articles provide instructions on creating new modules and publishing container images to a registry.
 
 ## Try the solution
 

articles/iot-edge/deploy-modbus-gateway.md

@@ -38,7 +38,7 @@ Unless otherwise specified, the procedures in this article do not explore all th
 ## Prerequisites
 
 * An Azure Repos repository. If you don't have one, you can [Create a new Git repo in your project](/azure/devops/repos/git/create-new-repo). For this article, we created a repository called **IoTEdgeRepo**.
-* An IoT Edge solution committed and pushed to your repository. If you want to create a new sample solution for testing this article, follow the steps in [Develop and debug modules in Visual Studio Code](how-to-vs-code-develop-module.md) or [Develop and debug C# modules in Visual Studio](./how-to-visual-studio-develop-module.md). For this article, we created a solution in our repository called **IoTEdgeSolution**, which has the code for a module named **filtermodule**.
+* An IoT Edge solution committed and pushed to your repository. If you want to create a new sample solution for testing this article, follow the steps in [Develop Azure IoT Edge modules using Visual Studio Code](tutorial-develop-for-linux.md). For this article, we created a solution in our repository called **IoTEdgeSolution**, which has the code for a module named **filtermodule**.
 
    For this article, all you need is the solution folder created by the IoT Edge templates in either Visual Studio Code or Visual Studio. You don't need to build, push, deploy, or debug this code before proceeding. You'll set up those processes in Azure Pipelines.
 

articles/iot-edge/how-to-continuous-integration-continuous-deployment-classic.md

@@ -37,7 +37,7 @@ Unless otherwise specified, the procedures in this article do not explore all th
 ## Prerequisites
 
 * An Azure Repos repository. If you don't have one, you can [Create a new Git repo in your project](/azure/devops/repos/git/create-new-repo). For this article, we created a repository called **IoTEdgeRepo**.
-* An IoT Edge solution committed and pushed to your repository. If you want to create a new sample solution for testing this article, follow the steps in [Develop and debug modules in Visual Studio Code](how-to-vs-code-develop-module.md) or [Develop and debug C# modules in Visual Studio](./how-to-visual-studio-develop-module.md). For this article, we created a solution in our repository called **IoTEdgeSolution**, which has the code for a module named **filtermodule**.
+* An IoT Edge solution committed and pushed to your repository. If you want to create a new sample solution for testing this article, follow the steps in [Develop Azure IoT Edge modules using Visual Studio Code](tutorial-develop-for-linux.md). For this article, we created a solution in our repository called **IoTEdgeSolution**, which has the code for a module named **filtermodule**.
 
   For this article, all you need is the solution folder created by the IoT Edge templates in either Visual Studio Code or Visual Studio. You don't need to build, push, deploy, or debug this code before proceeding. You'll set up those processes in Azure Pipelines.