Since updating to 1.25.10447 (before I was on 1.23.9750 or 1.24.10137 I don't remember) I have a very, very annoying thing happening... lots of times (90% of the times) I need to press F10 multiple times for the debugger to step just 1 line in code.

Just now I've do a simple test and I had to press F5 13 times for the debugger to continue.

Thanks for the feedback. Let me take a look at it and get back to you ASAP. If you could provide me with more information e.g. VS version, PHP version or anything that could help me replicate this would be helpful.

To link source code that resides in virtual machine I have Samba installed.Then in Windows I I create a virtual folder:mklink /d "E:\Podjetja\Nevron\Hospitality Interface\Design\PHP - VS2017\Iptv\Source" "\\192.168.200.254\Root\var\www\portal\library\Iptv"

So I get a Source folder under the project (unfortunately I couldn't make PHP tool to understand that files are on shared folder.. it would be cool if that could be possible).

I'm also getting a lot of "The program '[15784] php_remote.exe' has exited with code -1 (0xffffffff)."

Then in the middle of Single stepping if I wait a little I get a lot of:The program '[3880] php_remote.exe' has exited with code -1 (0xffffffff).Auto-attach to process '[16072] php_remote.exe' on machine 'WALDEMAR-PC' succeeded.The program '[10576] php_remote.exe' has exited with code -1 (0xffffffff).The program '[4104] php_remote.exe' has exited with code -1 (0xffffffff).The program '[15784] php_remote.exe' has exited with code -1 (0xffffffff).Auto-attach to process '[13832] php_remote.exe' on machine 'WALDEMAR-PC' succeeded....

I will have your environment recreated here and I will try to replicate this.

You can ignore the message from output pane. We should get rid of it as it's not important and "normal" during remote debugging.The program '[15784] php_remote.exe' has exited with code -1 (0xffffffff)."

I know you've already mentioned it, but it would help tremendously to know what version you had previously and if this worked there. So I can audit changes in the debuger since then.

Is there a way I could enable some kind of a log of your PHP tool and send the log file as pressing F5 30 #%@!#%@!#% times every time I want to continue is not the most productive way of spending the life.

I have also noticed this issue, but for me the stepping controls appear to work fine.

In my case the continue debugging (F5) button and hotkey seem to take a variable number of clicks/presses to actually continue the script. The number of clicks/presses required is usually 2-4, but has sometimes been higher. I have resorted to hitting it a bunch whenever I need to resume execution, but a proper solution would be preferable.