Databases
StackOverflow2013
Postsdbo
POWhen can an exception in a .NET WinForms app just get eaten without being caught or bubbling up to a windows exception?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhen can an exception in a .NET WinForms app just get eaten without being caught or bubbling up to a windows exception?
    primarykey
    data
    text
    <p>In several places in our code, we notice that if running under debugger it'll show that there's an unhandled exception in the code, however if running outside the debugger it will just ignore the exception completely as if it were caught. We have an exception handler that pops up an error submit dialog that's hooked up to Application.ThreadException and AppDomain.CurrentDomain.UnhandledException And neither of those appear to be catching them either. We also log our exceptions and nothing appears in the log.</p> <p>What are some possible reasons for this?</p> <p>Edit: It seems that it isn't dependent on the type of exception throw, but rather where it is thrown. This was tested by just adding:</p> <pre><code>throw new Exception("Test Exception"); </code></pre> <p>It'll show up under debugger but doesn't show up outside, so in our case it's not a ThreadAbortedException or anything that's dependent on it being a specific type of exception.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDavy8
    1. USDavy8
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhen can an exception in a .NET WinForms app just get eaten without being caught or bubbling up to a windows exception?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhen can an exception in a .NET WinForms app just get eaten without being caught or bubbling up to a windows exception?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhen can an exception in a .NET WinForms app just get eaten without being caught or bubbling up to a windows exception?
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo you have a "catch all" exception handler such as: AppDomain.CurrentDomain.UnhandledException += OnDomainExceptionThrown;
      singulars
      1. POWhen can an exception in a .NET WinForms app just get eaten without being caught or bubbling up to a windows exception?
      1. USRicardo Villamil
    2. COyes, that's mentioned in the question
      singulars
      1. POWhen can an exception in a .NET WinForms app just get eaten without being caught or bubbling up to a windows exception?
      1. USDavy8
    3. COI've got this happening as well. I can get it to happen if I explicitly throw any sort of exception in my main form's Form_Load event handler. In the debugger, it says it's unhandled, without the debugger, it just swallows it and moves on.
      singulars
      1. POWhen can an exception in a .NET WinForms app just get eaten without being caught or bubbling up to a windows exception?
      1. USYoopergeek
 

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