Hi, ve made a fresh install of PowerShell Plus (x64) (5.0.1130.0) on a new virtual Windows 2016 Server system.
Everything seems to work well, but i'm not able to set any breakpoints (F9 and Toggle not working, no entries in breakpoint list)
Execution policy is as follows CurrentUser BypassLocalMachine Remotesignedall others undefined
I'm admin on the server and the scripts used for testing were stored in different folders on the harddisk before.
Can anybody tell me how to change that behaviour? Thanks in advance
To use breakpoints, you must first save the script. Breakpoints will not work with an unsaved script same as ISE. This was a fundamental change to previous versions of PowerShellPlus that did not support PowerShell native breakpoints.
To set a breakpoint, you can either click on the gray vertical bar in the code editor or select the line and then click Toggle in the Breakpoints ribbon on the Execution tab.
To see the Breakpoints pane, select View tab and then either select Advance Layout or choose Custom Layout dropdown and select Breakpoints.
rrgiles, thanks for the fast reply. Even though it didn't help.Probably my explanation wasn't clear enough."the scripts used for testing were stored in different folders on the harddisk before" meant that the scrpits have already been stored for example in c:\Temp, c:\scripts and two other locations on the local hard disk.These scripts were opened in Powershell Plus but breakpoints can't be set. Even after successful execution (what automatically saves the script) i'm not able to set any breakpoints (not with Toggle, F9, context menu or else).And nothing becomes ever listed in the breakpoints pane.
Breakpoints worked well on a Windows 2008 system which i've used til now. So it seems to something related to the new OS version.
Based on the information you gave me I performed a test under the same conditions and was able to set a breakpoint as I specified in a previous post. I included $psversiontable output as well.The is a Windows Server 2016 Standard Hyper-V machine. I'm logged in as Admin as shown in the bottom right corner shield in PSP UI.
We're suddenly running into the same issue on W2K16. Trying to set the breakpoints no longer works on *some* scripts, but it does on others. This makes zero sense.
Running an uninstall and reinstalling to PSP v 5.0 (x64) didn't solve the issue, nor did running as administrator..
To do any research, I'd need one or more examples of scripts that will not allow breakpoints to be set and the line location in those scripts where a breakpoint was being attempted to be set. The current version of PSP uses the PowerShell internal breakpoint APIs that ISE also uses. This is the reason that files need to be first saved before breakpoints can be set. I'd also try the same breakpoint test with ISE to see if it mimics the same behavior.
Powered by IDERA