Skip to content

Commit 82fce7b

Browse files
Merge pull request #261132 from PatAltimore/patricka-module-dev-feedback
Add CLI pivot to EFLOW tutorial
2 parents 8e737a9 + 1e16960 commit 82fce7b

File tree

2 files changed

+209
-90
lines changed

2 files changed

+209
-90
lines changed

articles/iot-edge/how-to-visual-studio-develop-module.md

Lines changed: 5 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ This article shows you how to use Visual Studio 2022 to develop, debug, and depl
1717

1818
This article includes steps for two IoT Edge development tools.
1919

20-
* **Azure IoT Edge Dev Tool** CLI. This tool is preferred for development.
20+
* Command line interface (CLI) is the preferred tool for development.
2121
* **Azure IoT Edge tools for Visual Studio** extension. The extension is in [maintenance mode](https://github.com/microsoft/vscode-azure-iot-edge/issues/639).
2222

2323
Use the tool selector button at the beginning to choose your tool option for this article. Both tools provide the following benefits:
@@ -32,31 +32,13 @@ This article assumes that you use a machine running Windows as your development
3232

3333
* Install or modify Visual Studio 2022 on your development machine. Choose the **Azure development** and **Desktop development with C++** workloads options.
3434

35-
::: zone pivot="iotedge-dev-ext"
36-
37-
* Install the Azure IoT Edge Tools either from the Marketplace or from Visual Studio:
35+
* Download and install [Azure IoT Edge Tools](https://marketplace.visualstudio.com/items?itemName=vsc-iot.vs17iotedgetools) from the Visual Studio Marketplace. You can use the Azure IoT Edge Tools extension to create and build your IoT Edge solution. The preferred development tool is the command-line (CLI) *Azure IoT Edge Dev Tool*. The extension includes the Azure IoT Edge project templates used create the Visual Studio project. Currently, you need the extension installed regardless of the development tool you use.
3836

3937
> [!IMPORTANT]
4038
> The *Azure IoT Edge Tools for VS 2022* extension is in [maintenance mode](https://aka.ms/edgetool-dep). The preferred development tool is the command-line (CLI) *Azure IoT Edge Dev Tool*.
4139
42-
* Download and install [Azure IoT Edge Tools](https://marketplace.visualstudio.com/items?itemName=vsc-iot.vs17iotedgetools) from the Visual Studio Marketplace.
43-
* Or, in Visual Studio go to **Extensions > Manage Extensions**. The **Manage Extensions** popup opens. In the search box in the upper right, add the text **Azure IoT Edge Tools for VS 2022**, then select **Download**. Close the popup when finished.
44-
45-
You may have to restart Visual Studio.
46-
4740
> [!TIP]
48-
> If you are using Visual Studio 2019, download and install [Azure IoT Edge Tools for VS 2019](https://marketplace.visualstudio.com/items?itemName=vsc-iot.vs16iotedgetools) from the Visual Studio marketplace
49-
50-
::: zone-end
51-
52-
::: zone pivot="iotedge-dev-cli"
53-
54-
* Install the Python-based [Azure IoT Edge Dev Tool](https://pypi.org/project/iotedgedev/) to create your IoT Edge solution. There are two options:
55-
56-
* Use the prebuilt [IoT Edge Dev Container](https://github.com/Azure/iotedgedev/blob/main/docs/environment-setup/run-devcontainer-docker.md)
57-
* Install the tool using the [iotedgedev development setup](https://github.com/Azure/iotedgedev/blob/main/docs/environment-setup/manual-dev-machine-setup.md)
58-
59-
::: zone-end
41+
> If you are using Visual Studio 2019, download and install [Azure IoT Edge Tools for VS 2019](https://marketplace.visualstudio.com/items?itemName=vsc-iot.vs16iotedgetools) from the Visual Studio marketplace.
6042
6143
* Install the **Vcpkg** library manager
6244

@@ -170,7 +152,7 @@ Currently, the latest stable runtime version is 1.4. You should update the IoT E
170152

171153
::: zone pivot="iotedge-dev-cli"
172154

173-
1. In Visual Studio Code, open *deployment.debug.template.json* deployment manifest file. The [deployment manifest](module-deployment-monitoring.md#deployment-manifest) is a JSON document that describes the modules to be configured on the targeted IoT Edge device.
155+
1. Open *deployment.debug.template.json* deployment manifest file. The [deployment manifest](module-deployment-monitoring.md#deployment-manifest) is a JSON document that describes the modules to be configured on the targeted IoT Edge device.
174156
1. Change the runtime version for the system runtime module images *edgeAgent* and *edgeHub*. For example, if you want to use the IoT Edge runtime version 1.4, change the following lines in the deployment manifest file:
175157

176158
```json
@@ -483,7 +465,7 @@ In Visual Studio, open *deployment.debug.template.json* deployment manifest file
483465

484466
1. Replace the *image* property value with the module image name you pushed to the registry. For example, if you pushed an image tagged `myacr.azurecr.io/iotedgemodule1:0.0.1-amd64` for custom module *IotEdgeModule1*, replace the image property value with the tag value.
485467

486-
1. Add or replace the *createOptions* value with stringified content for each system and custom module in the deployment template.
468+
1. Add or replace the *createOptions* value with stringified content *for each system and custom module in the deployment template*.
487469

488470
For example, the IotEdgeModule1's *image* and *createOptions* settings would be similar to the following:
489471

@@ -510,7 +492,6 @@ az iot edge set-modules --hub-name my-iot-hub --device-id my-device --content ./
510492
>
511493

512494
::: zone-end
513-
<!--iotedgedev end-->
514495

515496
### Confirm the deployment to your device
516497

0 commit comments

Comments
 (0)