This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM. Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 7 years and 2 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
It's sad that we can not search for "Output" or "Write-Output" just in the Sapien Forum subjects - I'm pretty sure we are not the 1st Powershell Studio users with this problem...
If we *debug* a simple Powershell script in Powershell Studio:
"Hello Line 1"
"Hello Line 2"
Then we expect to get the Text "Hello Line 1" and "Hello Line 2" in the Output console.
But the Powershell Studio debugger changes the default Powershell handling of strings and they are not printed to the Output console.
We have to write this:
Write-Output "Hello Line 1"
Write-Output "Hello Line 2"
This is annyoing, because debugging should never change how a subject under test is handled.
Is there a way to get the default Powershell handling for strings in the Powershell Studio debugger?
So far, I've been unable to reproduce the results you're describing. This could be because I'm not understanding correctly so let me outline what I've tested to see where our paths differ:
Thank you very much for your fast and detailed answer!!,
Today, the problem disappeared and therefore I've spend some time to investigate it because I had the same behavior some weeks ago.
Using the following small change, I can reproduce the problem:
Strange Debug Session: Output "Hello 1" is missing
Debugsession1.png (51.08 KiB) Viewed 2554 times
This example leads to a delayed output: if you continue debugging, the missing output will appear.
I would have bet that I've got the situation where the output were completely missing, but today, I am not able to reproduce it.
I would like to verify real quick that the issue is your output isn't appearing in the Output panel when you hit the breakpoint in your screenshot, am I correct? I ask because your screenshot shows the Variables and Debug panel, and I wasn't sure if they were somehow related to this issue.
That aside, if the issue does crop up again please let us know and we'll look into further. It's usually when we want to reproduce a bug that we're unable to
Thank you very much for your feedback!,
yes, you're right, in my debug-session the Debug panel was active
and all strings were printed perfectly on the Output panel.
This topic is 7 years and 2 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.