dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update vscode-how-to-debug-multiple-dapr-apps.md

This commit is contained in:
greenie-msft 2021-07-23 09:06:12 -07:00 committed by GitHub
parent f50638db9e
commit cd62a4e487
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
daprdocs/content/en/developing-applications/ides/vscode/vscode-how-to-debug-multiple-dapr-apps.md
View File

@ -6,9 +6,7 @@ weight: 40000
description: "Learn how to configure VSCode to debug multiple Dapr applications"
---
As your project grows you may need to configure VS Code to debug multiple Dapr applications. This topic provides guidance on the steps you need to take.
To follow along with the breakdown of configuration features set up the [Hello World Quickstart Project](https://github.com/dapr/quickstarts/tree/v1.0.0/hello-world)
This doc provides guidance on the steps you need to take to configure VS Code to debug multiple Dapr applications. To follow along, set up the [Hello World Quickstart Project](https://github.com/dapr/quickstarts/tree/v1.0.0/hello-world).
## Step 1: Configure launch.json
This file contains information regarding the configurations you run during the debugging process. For the Hello World project, you have two applications running alongside 2 Dapr instances.
@ -56,11 +54,11 @@ Each supported language requires a specific configuration for launching the prog
}
```
The 3 main parameters each configuration needs are a `request`, `type` and `name`. They work as the basic parameters which help VS Code identify how to handle the task configurations you build later. For more information on VS Code debugging parameters visit the [VS Code launch attributes](https://code.visualstudio.com/Docs/editor/debugging#_launchjson-attributes)
The 3 parameters each configuration needs are a `request`, `type` and `name`. These parameters help VS Code identify how to handle the task configurations you build later. For more information on VS Code debugging parameters visit the [VS Code launch attributes](https://code.visualstudio.com/Docs/editor/debugging#_launchjson-attributes).
- `type` is related to the language you are trying to run, and depending on the language it might require an extension found in the marketplace, such as the [Python Extension](https://marketplace.visualstudio.com/items?itemName=ms-python.python).
- `name` is a unique name for the configuration, used for compound configurations when calling multiple configurations in your project.
- `${workspaceFolder}` is a VS Code variable reference, equal to the workspace path of the opened VS Code workspace.
- `type` is related to the language you are launching. Depending on the language, it might require an extension found in the marketplace, such as the [Python Extension](https://marketplace.visualstudio.com/items?itemName=ms-python.python).
- `name` is a unique name for the configuration. This is used for compound configurations when calling multiple configurations in your project.
- `${workspaceFolder}` is a VS Code variable reference. This is the path to the workspace opened in VS Code.
- The `preLaunchTask` and `postDebugTask` parameters refer to the program configurations run before and after launching the application. See step 2 on how to configure these.
## Step 2: Configure task.json
@ -69,7 +67,7 @@ You need to create the tasks mentioned in the launch.json for both application c
### Hello World daprd task
For the following tutorial you need to have the following parameters filled out "appId", "httpPort", "metricsPort", "label" and "type". There are more parameters depending on the specific Daprd command you're trying to run that you need such as "appPort" but those are dependent on what each application is trying to accomplish.
For the following tutorial, you need to have the following parameters filled out "appId", "httpPort", "metricsPort", "label" and "type". There are more parameters depending on the specific Daprd command you're running, such as "appPort", but those are dependent on what each application is trying to accomplish.
#### NodeJs task
@ -119,7 +117,7 @@ For the following tutorial you need to have the following parameters filled out
## Step 3: Configure compound launch inside launch.json
A compound launch configuration can be made in the launch.json and its purpose is to list the names of two or more launch configurations that should be launched in parallel. Optionally, a preLaunchTask can be specified and run before the individual debug sessions are started.
A compound launch configuration can be made in the launch.json. Its purpose is to list the names of two or more launch configurations that should be launched in parallel. Optionally, a preLaunchTask can be specified and run before the individual debug sessions are started.
For our example the compound configuration is be: