StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I'm not sure if I understand how this could be happening, but I have a very similar problem. The helper does not seem to show up for me either. THE BIG DIFFERENCE is that it just goes back to my form, no crashing, no windows exception, doesn't finish the sub, like I called an exit sub at that point or something.</p> <p>It's like this: I'm stepping through code and I reach a bit of bad code, I hit step into/over to execute the highlighted code, then all of a sudden my form is showing again, I can then interact with the form and continue as though nothing happened.... Especially annoying when I can't seem to see anything wrong in the code and I need the exception to tell me what went wrong (bad formatting string? incorrect types?)</p> <p>Running VS 2010 Premium on Windows 7 x64... from what I know, I've got debugger settings as default (for a debugged windows forms application). Using VB.Net, no data connections (unless you count an XML file - but that doesn't seem to cause it...) nothing really special about the code, I think a simple stack overflow [...] would cause it to happen. Anyone have the same experience?</p> <p>::Edit::<br> BTW, when it's not an obvious error, I put a try catch block around the spot that "has an exception" to catch the actual exception, then look at the caught exception in code - annoying, but it works!<br> ::Edit Again::<br> Well, I seem to have found out how to get exception helper - I think someone here mentioned they had exhausted this option already, but it fixed my problem: [Debug -> Exceptions -> "Break when an exception is:" -> Common Language Runtime Exceptions: Thrown] should be checked - doesn't seem to make sense why it would keep running though... oh well<br> ::End Edit::</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload