Can't debug multi-run dapr solution (The task dapr cannot be tracked)

[jasonshave]

Overview:

I'm able to run my dapr solution which has 3 ASP.NET 8 web API's using the dapr -f multi-run file but having some difficulty getting the debug experience to work.

Actual behavior:

When using the CTRL+SHIFT+P to scaffold a launch.json and task for tasks.json, it creates the following:

{
  "name": "Launch Dapr",
  "request": "launch",
  "type": "dapr",
  "runFile": "${workspaceFolder}/dapr.yaml",
  "preLaunchTask": "dapr"
}

{
  "label": "dapr",
  "type": "dapr",
  "runFile": "$(workspaceFolder)/dapr.yaml"
},

1. The first issue is that the runFile's value results in a file not found. If I remove the $(workspaceFolder) and just use dapr.yaml, the project starts up with the right components and sidecar/etc.
2. Once the solution is started, I get this error:

If I click DebugAnyway, I get:

3. If I use the dapr extension to locate the running apps and click on any of the debug buttons I get:

Expected behavior:

I should be able to attach and debug with breakpoints in each independent application.

[joshfreitas1984]

First up your tasks are wrong you can just do: { "label": "dapr", "type": "dapr", "runFile": "./dapr.yaml" }

Was getting the same error about fastlist so I downloaded it chucked it in the \vendor but then it never finds the process - I'm guessing somethings busted.

Is this extension abandoned?

[karpikpl]

same issue happening for me. that "runFile": "$(workspaceFolder)/dapr.yaml" is actually how DAPR extension scaffolds the project

[joshfreitas1984]

Anyone that finds this - pretty sure the plugin is abandoned. However, .NET Aspire is your friend! The f5 experience on the Apphost is amazing it will load up all your hosts and attach the debuggers super fast.

[philliphoff]

@joshfreitas1984 @karpikpl Abandoned, no. One item in an ever-increasing set of responsibilities with constantly shifting priorities, perhaps. :-) I'm working on a PR to resolve some of these task scaffolding issues.