Visual Studio Code debugger doesn't stop at breakpoints

5
votes

https://github.com/discord-bot-tutorial/Community-Discord-BOT The c# debugger for vscode doesn't stop at breakpoints with this specific project. I have tried creating a new project with dotnet new console dotnet restore
which worked correctly and I tried it with another project I created in Visual Studio Community 2017 which worked exactly as it should too.

launch.json and tasks.json https://gist.github.com/M4N1/daff738de1d5cbcf8cf3fdc461c3a83c

Update

I just tried the same thing on Ubuntu 18.04 (instead of win10) where it worked perfectly fine with the same version of vscode (1.28.1).

4
c#visual-studio-codevscode-debugger
Running the project in Release Mode? How do the breakpoints appear Solid filled Spheres or Hollow (ouline only) - later would mean dll & pdb/code is out of sync. - Prateek Shrivastava
The sphere is hollow. - Manuel Moser
Mouse hover that Sphere and it will tell you the problem. Your DLL (Binaries) are not in sync with the Source Code/PDB file. Clean-Rebuild the project. Then check the modified datetime of both the dll and corresponding pdb file. - Prateek Shrivastava
It says "Unverified breakpoint" - Manuel Moser
In Visual Studio everything is working fine. The problem is Visual Studio Code. - Manuel Moser

4 Answers

2
votes

If you have upgraded your .Net Core SDK recently, just update netcoreappX.X

 "program": "${workspaceFolder}/CommunityBot/bin/Debug/netcoreappX.X/CommunityBot.dll"

in launch.json file. Check your .Net Core SDK version by dotnet --version

1
votes

I use this configuration and work only if I insert this two line

// "stopOnEntry": true
// "justMyCode": false

{
  "version": "0.2.0",
  "configurations": [
    {
        "name": "Python: Debug Current File",
        "type": "python",
        "request": "launch",
        "program": "${file}",
        "console": "integratedTerminal",
        "stopOnEntry": true,
        "justMyCode": false
    },
  ]
}
0
votes

In VSCode 1.20 and 1.21 does not allow you to hit breakpoints. VSCode 1.18 works fine

If you are using VSCode 1.21 set the outFiles parameter in your launch config

Workaround - Try Deactivate then reactive breakpoints after debugging has started, Or, right click the breakpoints pane and "Reapply all breakpoints".

0
votes

I faced the same issue, I added debug mode to the argument list in the launch.json

  "version": "0.2.0",
  "configurations": [
    {
        "name": ".NET Core Launch (console)",
        "type": "coreclr",
        "request": "launch",
        "preLaunchTask": "build",
        "program": "${workspaceFolder}/bin/Debug/netcoreapp3.1/cs-scrapes.dll",


        "args": ["run",
            "debug"

        ],
        "cwd": "${workspaceFolder}",
        "console": "internalConsole",
        "stopAtEntry": false
    },
    {
        "name": ".NET Core Attach",
        "type": "coreclr",
        "request": "attach",
        "processId": "${command:pickProcess}"
    }
]