Debugging through the dotnet CLI tool

[rcdailey]

I don't really want paths to global tools in my launchSettings.json; I think this is just bad practice and also makes it difficult to support cross platform run configurations. I have the below launchSettings.json which works fine when I run it from Rider:

{
  "profiles": {
    "My.Lambda.Function": {
      "commandName": "Executable",
      "commandLineArgs": "lambda-test-tool-8.0 --port 5050",
      "executablePath": "dotnet"
    }
  }
}

However, I'm not able to hit breakpoints when I launch this run configuration from Jetbrains Rider using Debug mode. Is there some way I can use the dotnet CLI tool to kick off the test tool but still be able to attach to it for debugging breakpoints?

Thanks in advance.

[ashishdhingra]

@rcdailey Good afternoon. Please verify if you followed instructions below:

• Configure for JetBrains Rider.
• We also updated section Testing Executable Assemblies to elaborate steps for debugging.

Thanks,
Ashish