@itn3000 Thank you for the detailed report!
I was not able to reproduce this issue right away (I don't have win8 machine, but on win10 everything worked ok).
Could you please enable engine logging and post the output?

            ...
            "internalConsoleOptions": "openOnSessionStart",

            "logging": {
                "engineLogging": true
            },

            "pipeTransport": {
            ...

Also please enable debugger logs like this and attach them to this issue:

"debuggerPath": "g:/bin/netcoredbg/netcoredbg.exe --log=file"

(log files are created in TEMP folder, you can list them in PowerShell with ls $env:temp\netcore*)

from netcoredbg.

Thank you for replying, I made debug logs.
"netcoredbg-vscode-debugconsole.txt" is text from vscode's debug console.
netcoredbg-logs.zip

from netcoredbg.

After my investigating, I found I misunderstood the point at issue.

It is not depended on netfm, but on filename case.
In windows, drive letter of filename in pdb is large case when build with dotnet build,
but small case when specified project path with small case(like dotnet build c:\path\to\csproj).
This causes the filename unmatch in ResolveSequencePoint.

I replaced following point to x.Equals(y, StringComparison.OrdinalIgnoreCase), and found debugging works expectedly.

from netcoredbg.

@itn3000 Wow, that's really great that you found a solution! Would you be so kind to create a pull request with the fix?

from netcoredbg.

I created PR as #16, please review it.

from netcoredbg.

I still encounter issues with non-working breakpoints. The application is a ASP MVC (WebApi) app. Setting breakpoints using vsdbg work as expected.
Also setExceptionsBreakpoints fails, and I don't know why.

Edit: The same is the case for the default console app template.

Environment

Visual Code: 1.49.2
C# Extension: 1.23.2
Omnisharp: 1.37.1
netcoredbg: latest release build (Aug 20)
dotnet core sdk: 3.1.402
OS: Windows_NT x64 10.0.14393 (Windows Server 2016 Datacenter)

Steps to reproduce

The same as OP. Including the debug launch config.

Output

netcoredb_vscode.log

Unfortunately I don't really know where to start looking to help troubleshoot the issue further. So any guidance is appreciated.

Thank you!

from netcoredbg.

@smotti I updated netcoredbg sources, could you please check it?
If issue still here, please, open new issue instead.

from netcoredbg.