-
Notifications
You must be signed in to change notification settings - Fork 511
Write-Output does not display #151
New issue
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
Comments
We believe we know what the issue is. A fix for this should be forthcoming in a 0.5.1 release. |
Yep! This is something caused by some recent changes in VS Code's debugger interface. We're pretty sure that this will be fixed in 0.6.0 (to be released in a week or less). |
Just verified that this is fixed for 0.6.0. I'll close this bug once the update has shipped. |
0.6.0 is now released! Let me know if you run into any further trouble. |
v0.7.2 I'm using two Write-Output calls immediately after calling Invoke-RestMethod. The two statements output to the console as expected in ISE. When running the same script in VS Code, the two Write-Ouput statements don't output anything unless I set a break point on the first one and step over them one at a time. These two statements are at the end of the file. Here's a simple test:
|
Hey @dsmeltz, this is a known issue that we are investigating. You can subscribe to this issue to be notified of future updates: PowerShell/PowerShellEditorServices#138 |
v0.7.2 |
I've got a better way in mind to solve this problem, going to try and make it happen for the next big release (0.8.0)! |
When can we expect the next big release? |
I'm shooting for the first couple weeks of October. |
Example code below - nothing appears in the debug console until I set and disable a breakpoint. Write-Host works fine.
Function Get-MyProcess
{
$x = Get-Process -Name TabTip
Write-Output "$($x.ProcessName)"
}
Get-MyProcess
The text was updated successfully, but these errors were encountered: