Updates for new WASM extension version

Author: dominicbetts

articles/iot-operations/develop-edge-apps/howto-build-wasm-modules-vscode.md

@@ -26,7 +26,7 @@ The extension is supported on the following platforms:
 
 - Linux
 - Windows Subsystem for Linux (WSL)
-- Windows
+- Windows (be sure to use a Windows shell such as PowerShell or Command Prompt when when you run the extension commands on Windows)
 
 To learn more about graphs and WASM in Azure IoT Operations, see:
 
@@ -48,8 +48,8 @@ Development environment:
 Docker images:
 
 ```bash
-docker pull mcr.microsoft.com/azureiotoperations/processor-app:1.1.4
-docker tag mcr.microsoft.com/azureiotoperations/processor-app:1.1.4 host-app
+docker pull mcr.microsoft.com/azureiotoperations/processor-app:1.1.5
+docker tag mcr.microsoft.com/azureiotoperations/processor-app:1.1.5 host-app
 
 docker pull mcr.microsoft.com/azureiotoperations/devx-runtime:0.1.8
 docker tag mcr.microsoft.com/azureiotoperations/devx-runtime:0.1.8 devx
@@ -78,7 +78,9 @@ This command builds all the operators in the workspace and creates `.wasm` files
 
 ### Run the graph application locally
 
-Press `Ctrl+Shift+P` to open the command palette and search for **Azure IoT Operations: Run Application Graph**. Select **release** as the run mode. This command runs the graph application locally by using the local execution environment with the `graph.dataflow.yaml` file in the workspace.
+To start the local execution environment, press `Ctrl+Shift+P` to open the command palette and search for **Azure IoT Operations: Start Development Environment**. Select **release** as the run mode.
+
+When the local execution environment is running, press `Ctrl+Shift+P` to open the command palette and search for **Azure IoT Operations: Run Application Graph**. Select **release** as the run mode. This command runs the graph application locally by using the local execution environment with the `graph.dataflow.yaml` file in the workspace.
 
 It also reads from `hostapp.env.list` to set the environment variable `TK_CONFIGURATION_PARAMETERS` for data flow operator configuration parameters.
 
@@ -291,6 +293,8 @@ connections:
 
 Copy the `data` folder that contains the sample data from the cloned samples repository `explore-iot-operations\samples\wasm\data` to the current workspace. The `data` folder contains three JSON files with sample input temperature data.
 
+If you previously stopped the local execution environment, press `Ctrl+Shift+P` to open the command palette and search for **Azure IoT Operations: Start Development Environment**. Select **release** as the run mode.
+
 Press `Ctrl+Shift+P` to open the command palette and search for **Azure IoT Operations: Run Application Graph**:
 
 1. Select the `graph.dataflow.yaml` graph file.
@@ -352,13 +356,11 @@ You can modify the test data in the `data/` folder to experiment with different
 
 ### Build and run the state store scenario
 
-1. Press `Ctrl+Shift+P` to open the command palette and search for **Azure IoT Operations: Build All Data Flow Operators**.
-
-1. Select **release** as the build mode. Wait for the build to complete.
+If you previously stopped the local execution environment, press `Ctrl+Shift+P` to open the command palette and search for **Azure IoT Operations: Start Development Environment**. Select **release** as the run mode.
 
-1. Press `Ctrl+Shift+P` again and search for **Azure IoT Operations: Run Application Graph**.
+1. Press `Ctrl+Shift+P` to open the command palette and search for **Azure IoT Operations: Build All Data Flow Operators**. Select **release** as the build mode. Wait for the build to complete.
 
-1. Select **release** as the run mode.
+1. Press `Ctrl+Shift+P` again and search for **Azure IoT Operations: Run Application Graph**. Select **release** as the run mode.
 
 1. Select the `data` folder in your VS Code workspace for your input data. The DevX container launches to run the graph with the sample input.
 
@@ -435,6 +437,8 @@ The `data/` folder contains three test files:
 
 ### Build and run the schema registry scenario
 
+If you previously stopped the local execution environment, press `Ctrl+Shift+P` to open the command palette and search for **Azure IoT Operations: Start Development Environment**. Select **release** as the run mode.
+
 1. Press `Ctrl+Shift+P` to open the command palette and search for **Azure IoT Operations: Build All Data Flow Operators**.
 
 1. Select **release** as the build mode. Wait for the build to complete.
@@ -459,13 +463,14 @@ After processing completes:
 
 This example shows how the schema registry validates incoming messages and filters out messages that don't conform to the defined schema.
 
+Stop the local execution environment when you're done testing in release mode by pressing `Ctrl+Shift+P` and searching for **Azure IoT Operations: Stop Development Environment**.
+
 ## Debug WASM modules using the VS Code extension
 
 This example shows you how to debug WASM modules locally using breakpoints and the integrated debugger in VS Code.
 
 ### Prerequisites
 
-
 Complete the [Schema registry support for WASM modules](#schema-registry-support-for-wasm-modules) example to set up the sample workspace.
 
 ### Set up debugging
@@ -491,6 +496,8 @@ Complete the [Schema registry support for WASM modules](#schema-registry-support
 
 ### Run with debugging enabled
 
+Press `Ctrl+Shift+P` to open the command palette and search for **Azure IoT Operations: Start Development Environment**. Select **debug** as the run mode.
+
 1. Press `Ctrl+Shift+P` and search for **Azure IoT Operations: Run Application Graph**.
 
 1. Select the `lldb-debug.graph.dataflow.yaml` graph file.
@@ -501,15 +508,6 @@ Complete the [Schema registry support for WASM modules](#schema-registry-support
 
 1. After the DevX container launches, you see the host-app container start with an `lldb-server` for debugging.
 
-You use a special debug graph file because the current debugger can attach to only one custom WASM operator in a debug session. The dedicated debug graph lets you keep your normal `graph.dataflow.yaml` and prevents the debugger from attaching unpredictably when multiple modules exist.
-
-To create your own debug graph file:
-
-1. Copy your regular `graph.dataflow.yaml` to a new file. Using the `lldb-` prefix is a convention but the name is arbitrary.
-1. Remove all other custom WASM operators except the one you want to debug.
-1. Rebuild the target operator in **debug** mode so the symbols are available.
-1. Run the debug graph with run mode set to **debug**. The extension launches an `lldb-server` and attaches VS Code automatically.
-
 ### Debug the WASM module
 
 1. The execution automatically stops at the breakpoint you set in the `filter` function.
@@ -558,6 +556,8 @@ This debugging capability enables you to troubleshoot issues, understand data fl
 
 - **Host app stability**: The local execution environment might occasionally stop working and require restarting to recover.
 
+- **Remote debugging limitations**: Currently, you can't remotely debug WASM modules running in Azure Linux 3.0 due to incompatible LLDB versions.
+
 ## Troubleshooting
 
 ### Viewing logs