Why won't PowerShell ISE let me set breakpoints when running as Administrator?
powershell, powershell-2.0, powershell-ise
Solution
It looks like there's a problem with PowerShell and square brackets in folder and filenames.
Both PowerGUI and PowerShell ISE won't hit breakpoint if the script being debugged resides in a folder with `[` or `]` in the name.
Problem
Having failed to get PowerGUI to work properly I've fallen back on PowerShell ISE. However if I run this as Administrator it won't let me set any breakpoints. If I launch as normal (my login is a member of Administrators) all is well but because I need to script some tasks that require full administrator rights this is no good. I have saved the script as a proper file (i.e. it's not "untitled1.ps1") but no joy. I'm running Windows 7 x64 Ultimate. Strangely this doesn't seem to be a problem on my Windows 2008 R2 dev box (I'm logging in as user that is a member of Administrators then running PS ISE "As Administrator" and breakpoints are set and hit. Any ideas why this would be?