An page spawns multiple AJAX requests to receive data. All of them to the same URL with different parameters. The called PHP script calls different methods by the given parameters. If I set a breakpoint to one of them, the debug process stops for a short time. But the debugging stops when the second request is received.
If I set a breakpoint to one of them, the debug process stops for a short time. But the debugging stops when the second request is received. It first breaks normally, but stops debugging when the second request is received
Thank you for the issue! CCing @MiloslavBeno who might help (please give us few days)
I've noticed that as well, but wouldn't know of a good way to handle asynchronous debugging. That's just not something we as humans could even do. Although, it might be better to not accept new debugging requests when one is currently active.
Nicely said @MarcHenderkes :) although we already have async debugging in Visual Studio, we'll improve that for VSCode as well for sure. (CC @MiloslavBeno)
Do we? Whenever I hit multiple requests all it leads to is the need to press F10 a billion times to hit the next line of code. What's the expected behaviour?
This might be caused when using the PHP's built-in server. It handles only one request at a time and enqueues the others.
If you're running Apache, IIS or others, it is probably an unexpected behavior.
Using Apache as a web server so that makes sense. It's a minor inconvenience anyway, I just close the tab and reopen it when that happens.
This might be caused by multiple ajax requests to php. Currently, we consider multiple requests as individual processes, which are handled by a not very intuitive way in Visual Studio. Please take a look here https://docs.devsense.com/en/vs/debugging/stepping#stepping-when-debugging-multiple-requestsprocesses
It might be better in the future to handle the requests differently, e.g. as C# handles multiple threads.
Thank you
Oh, that's great. Is there a way to stop VS from accepting consequent debugging requests after you've started debugging the first, or maybe second one?