Why does "F5 - Start Debugging" ignore breakpoints in PowerGUI?

Question

I'm not sure I'm a little fat, but I have a simple script with three lines:

$iis = 90000
$name = "somesite"
Write-Host("Values are: $iis and $name")

If I set a breakpoint on any of these lines and press the play button (F5 - start debugging), the script is executed, but the breakpoints are ignored.

If I run the script using F11 (step by step), I can only execute the penalty, however, pressing F5 to go to the next breakpoint causes PowerGUI to ignore the breakpoints

The script I'm working on is substantial, and I really don't want to have F11 through every line of code.

Why should it be?

• I am running PowerGUI 2.2.0.1358 on a 64-bit version of Windows 7 Ultimate Edition.
• I tried both the x64 and x32 versions of the PowerGUI script editor without success.
• PowerGUI script ( PowerGUI script " " )
• My PowerShell ​​ Unrestricted.

Answer 1

, PowerShell .

PowerGUI, PowerShell ISE , script [ ] .

Answer 2

, script, , . . \\serverA\FileShare\script.ps1.

script c:\script\script.ps1, .

Answer 3

Powershell also seems to have problems with spaces in folder names. I didn’t like My Documents, but for Documents. As soon as I switched my path in PowerShell to ISE, the debugger worked again.