Databases
StackOverflow2013
Postsdbo
POException handling with multiple forms
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POException handling with multiple forms
    primarykey
    data
    text
    <p>I'm seeing different behavior with exceptions being caught or not being caught when I am debugging vs. when I am running a compiled .exe. I have two forms (Form1 and Form2). Form1 has a button on it which instantiates and calls ShowDialog on Form2. Form2 has a button on it which intentionally produces a divide by zero error. When I'm debugging, the catch block in Form1 is hit. When I run the compiled .exe, it is NOT hit, and instead I get a message box that states, "Unhandled exception has occurred in your application. If you click continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately...Attempted to divide by zero". My question is why do you get different behavior when debugging vs. when running the .exe? If that is the expected behavior, then would it be considered necessary to put try/catch blocks in every single event handler? That seems kind of crazy over kill, doesn't it?</p> <p>Here's the code for Form1. </p> <pre><code>public partial class Form1 : Form { public Form1() { InitializeComponent(); } private void button1_Click(object sender, EventArgs e) { try { Form2 f2 = new Form2(); f2.ShowDialog(); } catch(Exception eX) { MessageBox.Show( eX.ToString()); //This line hit when debugging only } } } </code></pre> <p>Here's Form2's code:</p> <pre><code>public partial class Form2 : Form { public Form2() { InitializeComponent(); } private void button1_Click(object sender, EventArgs e) { int x = 0; int y = 7 / x; } } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POException handling with multiple forms
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POException handling with multiple forms
      1. USJason Down
      1. VTFavorite
    3. VO
      singulars
      1. POException handling with multiple forms
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTime to call on Skeeter or Gravell!
      singulars
      1. POException handling with multiple forms
      1. USJason Down
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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