ASP Apps keep running after stop
I've noticed something strange in the design environment when working with ASP applications: the STOP button does not seem to work the same way it does with Windows applications. And this is not simply caused by me confusing the STOP button with the PAUSE button, OK? PAUSE will not allow me to see the result of code changes - a rebuild is always necessary anyway, so I want to STOP execution, not PAUSE it.
While all of the browser windows are being closed as expected, it appears as though VS is retaining the current point of execution, call stacks, and variable values when STOP is pressed in the middle of execution. Clicking Play appears to try to rebuild (taking longer each time I do this), but suddenly the code starts running below the line where I clicked STOP earlier. There should be no way it can even get to this code at this point, yet it appears to continue running as though I clicked PAUSE instead of STOP.
Whether this is how it's supposed to work or not, it is forcing me to shut down and reopen VS when I have to do this. It's either that or wait until this code finishes executing, which takes a long time assuming it doesn't throw an error of some kind. This is a frustrating waste of time just to clear the call stack so it doesn't resume execution after STOP and PLAY are clicked!
So, is there some way to force VS to reset the stacks and variables when STOP is clicked so I don't have to go through this every time I stop execution? Did I accidentally turn on some option that equates the STOP button with the PAUSE button? Or am I stuck restarting VS when I want to do this because it's incapable of clearing it's execution stack otherwise?
|
