Windows PowerShell Home
Editor locks out ALL scripts while one script is being debugged
11/19/2012 4:44:46 PM
User(s) can reproduce this bug
Powershell ISE locks out ALL scripts while one script is being debugged. This makes life unfun, but has an easy workaround. Opening a second ISE allows the other script to be debugged, but this would mean that I would need to open an ISE for every script I am working on (I can easily find myself working on three scripts). I base my opinion on this being a bug because I use VBSEdit, PowerGUI, and Visual Studio and none of them exhibit this behavior (although the only pertinent one should be VS). I also hear that Sapien does not exhibit this behavior. Given all that I would think that this shouldn't be a by design (I would find it odd if someone specically designed the program to lock out other scripts, but that is just my .02).
How often does this happen?
Have you seen this problem before in this product?
I don't know if this issue existed previously
Open powershell ISE
Open two scripts
Create breakpoint in first script
Debug first script
Note that second script (and all other scripts) show 'Read Only'.
Ideally, I would prefer that NO script be locked out while one is being debugged, not even the script you are debugging (as in Visual Studio), but minimally I would like to see that only the script I am debugging is affected by the debugging process.
to post a comment.
Please enter a comment.
to post a workaround.
Please enter a workaround.
on 11/19/2012 at 4:45 PM
Open an ISE for every script. Not pretty, but does the trick.
© 2013 Microsoft