If you use Smalltalk, you just put a halt right there in the SSP page - into the normal Smalltalk debugger you go. Over in ASP Land, it's a trifle more complicated than that. But hey, rebooting every few minutes probably aids your productivity, right?
Smalltalk, on the page: <% self halt. %>
or, over in ASP-Land:
Here's the drill. What I discovered yesterday while frustrated enough to physically throw my laptop out the nearest window.
- Start debugger.
- Wait until the process load starts, then HANGS.
- Open Task Manager.
- KILL aspnet_wp.exe.
- New aspnet_wp.exe starts.
- Process continues to load in debugger.
ICK! I had this problem while working at Paramount. I never did figure out the real fix for it. This will work for a couple of debugging sessions, then you get to reboot the machine.
And they call this the future... You could also ponder Seaside...