We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
$PSVersionTable
Copy / paste the following commands into the PowerShell Integrated Console, and paste the output here: code-insiders -v 1.18.0-insider 82dcf9835265cd0a45ec135587ae2a82673f1c8f PS Git:\> $pseditor.EditorServicesVersion Major Minor Build Revision ----- ----- ----- -------- 1 4 1 0 PS Git:\> code --list-extensions --show-versions austin.vscode-twitter@0.7.1 bradygaster.azuretoolsforvscode@1.3.0 DougFinke.vscode-PSStackoverflow@0.0.2 eamodio.gitlens@5.4.1 formulahendry.docker-explorer@0.1.5 johnpapa.azure-functions-tools@0.3.1 ms-mssql.mssql@1.2.0 ms-vscode.PowerShell@1.4.3 msazurermtools.azurerm-vscode-tools@0.3.7 PeterJausovec.vscode-docker@0.0.18 stefanstranger.vscode-psconfeu2017@1.0.5 PS Git:\> $PSVersionTable Name Value ---- ----- PSVersion 5.1.16299.19 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.16299.19 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1
$psEditor.Workspace.NewFile() does nothing in latest code-insiders (updated today)
Follow the instructions in the README about capturing and sending logs.
The text was updated successfully, but these errors were encountered:
Thanks Rob! I'll take a look.
Sorry, something went wrong.
Fix PowerShell#1060: .Workspace.NewFile doesn't work in VSC 1.18+
94bd729
ccebc4d
No branches or pull requests
System Details
$PSVersionTable
:Issue Description
$psEditor.Workspace.NewFile() does nothing in latest code-insiders (updated today)
Attached Logs
Follow the instructions in the README
about capturing and sending logs.
The text was updated successfully, but these errors were encountered: