Current master branch cannot debug PowerShell files

[corbob]

System Details

System Details Output

### VSCode version: 1.32.0-insider aeaef41d51201e555735f5e8d2f38a9d0ddb9026 x64

### VSCode extensions:
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]


### PSES version: 2.0.0.0

### PowerShell version:

Name                           Value
----                           -----
PSVersion                      5.1.18836.1000
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.18836.1000
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

I am experiencing a problem with debugging PowerShell scripts when building master after commit f0886cd

Steps I have taken to reproduce issue:

1. clone PSES Master and vscode-powershell master to fresh directories
2. In vscode-powershell directory run: git checkout f0886cd9edf58e12c612a2
3. Launch Extension from vscode (stable or insiders)
4. Open a PowerShell file
5. Why can't I F5???

Note: F8 works just fine.

Expected Behaviour

It should debug the script

Actual Behaviour

It doesn't appear to do anything.

Attached Logs

1550730182-someValue.sessionId.zip

[corbob]

Was discussing this with a coworker and I noticed this change: f0886cd#diff-b9cfc7f2cdf78a7f4b91a753d10865a2R311 I can't fathom is being the cause, but at this point I'll take anything. Just adding this comment in case anyone else is taking a look and can test changing this line to lowercase powershell 🤷‍♂️

[rkeithhill]

Hmm, I'll take a look at this over the weekend. Been busy trying to get a posh-git 1.0.0-beta3 release ready.

[rkeithhill]

I've updated to latest on master and I can see my changes to package.json. But when I debug the extension, I can debug just fine from the extension host. Not sure what is going on but I certainly do not see a "launch" requests in your log file. Can you describe which debug config you are using? PoweShell Launch Current File, PowerShell Interactive Session? Maybe you could paste the debug config json you're using here?

[rkeithhill]

Well, on my laptop I can repro this. I have a "fix" but I'd like to understand a little better why this isn't working. Will have a PR in the next day or two.