.NET Core attach debugger template defaults to "processname" and the flydown says use "pid"

[jeffschwMSFT]

When you try to debug attach a .NET Core application the default launch.json has "processname", but if you use "dotnet" it says it has found multiple and you need to use "pid". But in reality you need to use "processId". I recommend that we change the default template to replace "processName" with "processId" and update the fly down text to use "processId" instead of "pid".

[gregg-miskelly]

Sounds reasonable. @caslan @DustinCampbell anyone have an opinion as to if we should change this for RC2?

[DustinCampbell]

It'd be nice to make it work. 😄

[caslan]

It's very low risk so I'm in favor of changing especially now running apps via dotnet ... is more common

[gregg-miskelly]

Yes, should be ~0 risk.

[gregg-miskelly]

@MattGertz are you okay taking this?

[MattGertz]

I'm OK but it will need an escrow check from Dmitry/JoC.

[MattGertz]

Talked with Gregg offline; I didn't realize that there was a distinct part from the error message change. This won't meet an escrow bar; we can pick it up afterwards.

[DustinCampbell]

Sounds good. Anyway, there'll be interim releases available that we can point customers to afterward.

[caslan]

Fixed with #197

[kerryjiang]

Was this issue fixed?
I tried the v1.0.5-rc2, it still stays there.

[DustinCampbell]

@kerryjiiang: It is fixed in the dev branch in our RTM milestone.