Anyone notice how .net still runs code after you hit "stop"?
(Sorry, worded the subject wrong... should be "the Visual Studio .net 2003 Debugger" instead of plain ol' ".net")
What's up with this?
Say you breakpoint a line and have some code underneath that inserts a few records into a table in a database.
Lines go somewhat like this:
init variables
open db connection
insert records
close db connection
If you breakpoint on the init variables part and step through the code and realize "oh, I just spotted an error in my code" and hit stop, all the code beyond that is still executed, or in this case, records will be inserted into the table.
Why does it do this? Isn't that potentially dangerous in the sense that even though you spotted the error and hit stop, your code will still follow through?
Basically it kinda sucks for me right now because I need to run this app and breakpoint it to see how data will look before going in, but in order to prevent it from actually executing the SP, I have to rename it on the server so when it's called, it errors out.
__________________
I love lamp.
Last edited by Stompy; 08-07-2004 at 10:22 AM..
|