StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POVisual Studio does not break with exception assistant, but just stops the process
text
Body
copied!<p>Usually, Visual Studio breaks if it encounters an unhandled exception and shows an exception assistant window. </p> <p>But in some occasions, Visual Studio instead just stops the program that was running and does not break or show the exception helper.</p> <p>The exception options (Ctrl+Alt+E) are configured correctly: "user-unhandled" is checked on all items, "thrown" is unchecked. In the debugging options, i have enabled the exception assistant. </p> <p>Because it only happens on some occassions, i tried to figure out when visual studio enters its "malfunctioning exception assistant state". </p> <p>EDIT:</p> <p>It looks like the malfunctioning exception assistant ghost only shows up in winforms applications, and only after there has been some external action like calling a web service or opening a database connection.</p> <p>END EDIT</p> <blockquote> <p>It turns out the exception assistant works fine until an ADODB connection is opened:</p> <pre><code>var conn = new ADODB.Connection(); conn.Open("Provider=SQLOLEDB;Server=localhost;Database=db;UID=user;PWD=pw;", "", "", -1); throw new InvalidOperationException(); </code></pre> <p>After excecuting the conn.Open statement, the exception assistant will never kick in.</p> </blockquote> <p>Does this sound familiar to anyone, and, more important: does anyone have a solution for the problem? As you can imagine, debugging an application becomes very hard if the application always just quits on exceptions.</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