Debugger reports errors when running script with improperly encoded characters

System Details

• Operating system name and version:
• VS Code version: 1.13.0
• PowerShell extension version: 1.3.2
• Output from $PSVersionTable:

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

Copy / paste the below commands into the PowerShell Integrated Terminal, and paste the output here

code -v $pseditor.EditorServicesVersion code --list-extensions --show-versions $PSVersionTable

PS C:\gd\Documents\s\docker\tools\vstsagent> code -v
1.13.0
376c52b955428d205459bea6619fc161fc8faacf
PS C:\gd\Documents\s\docker\tools\vstsagent> $pseditor.EditorServicesVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
1      3      2      0


PS C:\gd\Documents\s\docker\tools\vstsagent> code --list-extensions --show-versions
DotJoshJohnson.xml@1.8.0
mkloubert.vs-deploy@9.25.0
ms-vscode.csharp@1.10.0
ms-vscode.PowerShell@1.3.2
PeterJausovec.vscode-docker@0.0.16

Issue Description

Configuration below will throw powershell engine off and will report errors below

Configuration test {
    Script DockerConfigFile {
        TestScript = {
            return $true;
        }
        GetScript = {
          
            return {@{configValue = "dd"}
            }
        }
        SetScript = {
            $dockerConfig | Add-Member –MemberType NoteProperty –Name graph –Value $graphLocation
               
        }
    }
}
Test

Errors reported during run

At C:\gd\Documents\s\docker\tools\vstsagent\test.ps1:12 char:82
+ ... ember –MemberTypeNoteProperty –Name graph –Value $graphLocation
+                                                     ~~~~~~~~~~~~~~~~~~~~~
The string is missing the terminator: ".

At C:\gd\Documents\s\docker\tools\vstsagent\test.ps1:11 char:21
+         SetScript = {
+                     ~
Missing closing '}' in statement block or type definition.

At C:\gd\Documents\s\docker\tools\vstsagent\test.ps1:17 char:5
+ Test
+     ~
There is an incomplete property assignment block in the instance definition.

At C:\gd\Documents\s\docker\tools\vstsagent\test.ps1:1 char:20
+ Configuration test {
+                    ~
Missing closing '}' in statement block or type definition.

[Eickhel]

Great work @tylerl0706! thanks for confirm the bug… I guess it’s time to move to PS Core 😉

[TylerLeonhardt]

Ah. I’ve got a repro!

It’s only on Windows PowerShell and this is, in fact, a Windows PowerShell bug. Here’s why:

let’s say we have @Eickhel’s example:

function Convert-Exceptions {
    param ([String]$src = [String]::Empty)
    $src -replace "el medano", "el médano"
}

Convert-Exceptions("el medano")

With the PowerShell ISE, when you have an untitled file and hit F5, it does the same thing as if you selected all the text and hit F8 (aka ctrl-A, F8).

If you save the file to something, like test.ps1 it runs the actual file like so:

Notice the bad formatting!

VSCode runs the file that you are F5’ing as well:

PS C:\Users\tylerleonhardt\Desktop> c:\Users\tylerleonhardt\Desktop\test.ps1

If we run that exact line in Windows PowerShell as well we get the same wrong formatting:

If we try this is PowerShell Core 6, the bug was fixed and the output is what we expect:

Moral of the story, this is a bug in Windows PowerShell and not the PowerShell extension for VSCode.