From 669fa54b10ede7895f335800cc86b00348dfdb05 Mon Sep 17 00:00:00 2001 From: jasonviviano <83607984+jasonviviano@users.noreply.github.com> Date: Thu, 15 Jul 2021 10:37:03 -0400 Subject: [PATCH] Fixed vscode link and updated information on manual. --- .../ides/{visual-studio-code => vscode}/_index.md | 0 .../vscode-dapr-extension.md | 0 .../vscode-manual-configuration.md | 8 ++++---- .../vscode-remote-dev-containers.md | 4 ++-- 4 files changed, 6 insertions(+), 6 deletions(-) rename daprdocs/content/en/developing-applications/ides/{visual-studio-code => vscode}/_index.md (100%) rename daprdocs/content/en/developing-applications/ides/{visual-studio-code => vscode}/vscode-dapr-extension.md (100%) rename daprdocs/content/en/developing-applications/ides/{visual-studio-code => vscode}/vscode-manual-configuration.md (83%) rename daprdocs/content/en/developing-applications/ides/{visual-studio-code => vscode}/vscode-remote-dev-containers.md (85%) diff --git a/daprdocs/content/en/developing-applications/ides/visual-studio-code/_index.md b/daprdocs/content/en/developing-applications/ides/vscode/_index.md similarity index 100% rename from daprdocs/content/en/developing-applications/ides/visual-studio-code/_index.md rename to daprdocs/content/en/developing-applications/ides/vscode/_index.md diff --git a/daprdocs/content/en/developing-applications/ides/visual-studio-code/vscode-dapr-extension.md b/daprdocs/content/en/developing-applications/ides/vscode/vscode-dapr-extension.md similarity index 100% rename from daprdocs/content/en/developing-applications/ides/visual-studio-code/vscode-dapr-extension.md rename to daprdocs/content/en/developing-applications/ides/vscode/vscode-dapr-extension.md diff --git a/daprdocs/content/en/developing-applications/ides/visual-studio-code/vscode-manual-configuration.md b/daprdocs/content/en/developing-applications/ides/vscode/vscode-manual-configuration.md similarity index 83% rename from daprdocs/content/en/developing-applications/ides/visual-studio-code/vscode-manual-configuration.md rename to daprdocs/content/en/developing-applications/ides/vscode/vscode-manual-configuration.md index ad57dc7de..c2585e180 100644 --- a/daprdocs/content/en/developing-applications/ides/visual-studio-code/vscode-manual-configuration.md +++ b/daprdocs/content/en/developing-applications/ides/vscode/vscode-manual-configuration.md @@ -22,7 +22,7 @@ Using the [tasks.json](https://code.visualstudio.com/Docs/editor/tasks) and [lau #### Modifying launch.json configurations to include a preLaunchTask -In your [launch.json](https://code.visualstudio.com/Docs/editor/debugging) file add a [preLaunchTask](https://code.visualstudio.com/Docs/editor/debugging#_launchjson-attributes) for each configuration that you want daprd launched. The [preLaunchTask](https://code.visualstudio.com/Docs/editor/debugging#_launchjson-attributes) will reference tasks that you define in your tasks.json file. Here is an example for both Node and .NET Core. Notice the [preLaunchTasks](https://code.visualstudio.com/Docs/editor/debugging#_launchjson-attributes) referenced: daprd-web and daprd-leaderboard. +In your [launch.json](https://code.visualstudio.com/Docs/editor/debugging) file add a [preLaunchTask](https://code.visualstudio.com/Docs/editor/debugging#_launchjson-attributes) for each configuration that you want daprd launched. The [preLaunchTask](https://code.visualstudio.com/Docs/editor/debugging#_launchjson-attributes) references tasks that you define in your tasks.json file. Here is an example for both Node and .NET Core. Notice the [preLaunchTasks](https://code.visualstudio.com/Docs/editor/debugging#_launchjson-attributes) referenced: daprd-web and daprd-leaderboard. ```json { @@ -64,17 +64,17 @@ In your [launch.json](https://code.visualstudio.com/Docs/editor/debugging) file #### Adding daprd tasks to tasks.json -You will need to define a task and problem matcher for daprd in your [tasks.json](https://code.visualstudio.com/Docs/editor/tasks) file. Here are two examples (both referenced via the [preLaunchTask](https://code.visualstudio.com/Docs/editor/debugging#_launchjson-attributes) members above). Notice that in the case of the .NET Core daprd task (daprd-leaderboard) there is also a [dependsOn](https://code.visualstudio.com/Docs/editor/tasks#_compound-tasks) member that references the build task to ensure the latest code is being run/debugged. The [problemMatcher](https://code.visualstudio.com/Docs/editor/tasks#_defining-a-problem-matcher) is used so that VSCode can understand when the daprd process is up and running. +You need to define a task and problem matcher for daprd in your [tasks.json](https://code.visualstudio.com/Docs/editor/tasks) file. Here are two examples (both referenced via the [preLaunchTask](https://code.visualstudio.com/Docs/editor/debugging#_launchjson-attributes) members above). Notice that in the case of the .NET Core daprd task (daprd-leaderboard) there is also a [dependsOn](https://code.visualstudio.com/Docs/editor/tasks#_compound-tasks) member that references the build task to ensure the latest code is being run/debugged. The [problemMatcher](https://code.visualstudio.com/Docs/editor/tasks#_defining-a-problem-matcher) is used so that VSCode can understand when the daprd process is up and running. Let's take a quick look at the args that are being passed to the daprd command. -* -app-id -- the id (how you will locate it via service invocation) of your microservice +* -app-id -- the id (how you locate it via service invocation) of your microservice * -app-port -- the port number that your application code is listening on * -dapr-http-port -- the http port for the dapr api * -dapr-grpc-port -- the grpc port for the dapr api * -placement-host-address -- the location of the placement service (this should be running in docker as it was created when you installed dapr and ran ```dapr init```) ->Note: You will need to ensure that you specify different http/grpc (-dapr-http-port and -dapr-grpc-port) ports for each daprd task that you create, otherwise you will run into port conflicts when you attempt to launch the second configuration. +>Note: You need to ensure that you specify different http/grpc (-dapr-http-port and -dapr-grpc-port) ports for each daprd task that you create, otherwise you run into port conflicts when you attempt to launch the second configuration. ```json { diff --git a/daprdocs/content/en/developing-applications/ides/visual-studio-code/vscode-remote-dev-containers.md b/daprdocs/content/en/developing-applications/ides/vscode/vscode-remote-dev-containers.md similarity index 85% rename from daprdocs/content/en/developing-applications/ides/visual-studio-code/vscode-remote-dev-containers.md rename to daprdocs/content/en/developing-applications/ides/vscode/vscode-remote-dev-containers.md index d3409a88e..3235d30b1 100644 --- a/daprdocs/content/en/developing-applications/ides/visual-studio-code/vscode-remote-dev-containers.md +++ b/daprdocs/content/en/developing-applications/ides/vscode/vscode-remote-dev-containers.md @@ -1,6 +1,6 @@ --- type: docs -title: "Visual Studio Code remote dev containers" +title: "Developing Dapr applications with remote dev containers" linkTitle: "Remote dev containers" weight: 20000 description: "How to setup a remote dev container environment with Dapr" @@ -8,7 +8,7 @@ description: "How to setup a remote dev container environment with Dapr" The Visual Studio Code [Remote Containers extension](https://code.visualstudio.com/docs/remote/containers) lets you use a Docker container as a full-featured development environment without installing any additional frameworks or packages to your local filesystem. -Dapr has pre-built Docker remote containers for each of the language SDKs. You can pick the one of your choice for a ready made environment. Note these pre-built containers automatically update to the latest Dapr release. +Dapr has pre-built Docker remote containers for NodeJS and C#. You can pick the one of your choice for a ready made environment. Note these pre-built containers automatically update to the latest Dapr release. ### Setup a remote dev container