Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debugger: Error processing lanuch options at filed: processId #1279

Closed
qian6 opened this issue Mar 3, 2017 · 3 comments
Closed

Debugger: Error processing lanuch options at filed: processId #1279

qian6 opened this issue Mar 3, 2017 · 3 comments

Comments

@qian6
Copy link

qian6 commented Mar 3, 2017

Environment data

dotnet --info output:
VS Code version: 1.10.1
C# Extension version: \scratch2\scratch\janraj\vsdbg3\csharp-1.8.0-beta1.vsix
.NET Core SDK: 1.0.0-preview2-1-003177
OS: Windows 10

Steps to reproduce

  1. Open attached folder.
    hwapp.zip
  2. Select '.NET Core Attach'.
  3. Set a breakpoint at line of 17 in Program.cs.
  4. Use command to "dotnet run" process.
  5. Press F5 to select process and start debugging.

Expected behavior

It can normal debug and hit in 17 line.

Actual behavior

capture

Investigation

1.This issue repro on all platforms.

@rajkumar42
Copy link
Contributor

Fix is to change the attach templates from
"processId": "${command.pickProcess}"
to
"processId": "${command:pickProcess}"

Note, the change from dot to colon. Same goes for remote attach.

@gregg-miskelly
Copy link
Contributor

In that case this is related to #1275.

I guess we could make an improved error message if we wanted.

@gregg-miskelly
Copy link
Contributor

We discussed it and we think that the squiggles you get from VS Code should be good enough for folks who have pre-existing launch.json files to understand the problem. So we are resolving this as 'By Design' for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants