-
Notifications
You must be signed in to change notification settings - Fork 8.4k
VSCode corrupts 'registered sign' character #2851
Copy link
Copy link
Closed
Labels
Resolution-FixedThe issue is fixed.The issue is fixed.Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Maintainers-Buildspecific to affecting the buildspecific to affecting the build
Metadata
Metadata
Assignees
Labels
Resolution-FixedThe issue is fixed.The issue is fixed.Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Maintainers-Buildspecific to affecting the buildspecific to affecting the build
Type
Fields
Give feedbackNo fields configured for issues without a type.
The Issue was opened in VSCode repo microsoft/vscode#15303 and closed with resolution:
Ex. CoreAdapter.cs
Microsoft.PowerShell.Utility.psd1
Root of the problem is that VS Code default encoding is UTF8 and at the same time, most of the files in the Powershell repo is ASCII. (This problem does not exist in Visual Studio and Notepad++)
VS Code is recommended for the Powershell repo. So we would fix the problem here.