Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>An <code>AppDomain.UnhandledException</code> handler is wired as: </p> <pre><code>AppDomain.CurrentDomain.UnhandledException += CurrentDomain_UnhandledException; </code></pre> <p>But I could not find a way to flag as handled in the handler - so this always seems to result in an app shut down no matter what you do. So I do not think this is a lot of use. </p> <p>Better to handle <code>Application.Current.DispatcherUnhandledException</code> and to test for <code>CommunicationObjectFaultedException</code> - as you can recover from that by just re-initializing your proxy - exactly as you did at initial connection. E.g: </p> <pre><code>void Current_DispatcherUnhandledException(object sender, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs e) { if (e.Exception is CommunicationObjectFaultedException) { //|| e.Exception is InvalidOperationException) { Reconnect(); e.Handled = true; } else { MessageBox.Show(string.Format("An unexpected error has occured:\n{0}.\nThe application will close.", e.Exception)); Application.Current.Shutdown(); } } public bool Reconnect() { bool ok = false; MessageBoxResult result = MessageBox.Show("The connection to the server has been lost. Try to reconnect?", "Connection lost", MessageBoxButton.YesNo); if (result == MessageBoxResult.Yes) ok = Initialize(); if (!ok) Application.Current.Shutdown(); } </code></pre> <p>where Initialize has your initial proxy instantiation/connection code.</p> <p>In the code you posted above I suspect that you are handling <code>DispatcherUnhandledException</code> <strong>twice</strong> - by wiring a handler in xaml AND in code.</p>
    singulars
    1. This table or related slice is empty.
    1. POShould use both AppDomain.UnhandledException and Application.DispatcherUnhandledException?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRicibob
    1. USRicibob
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm also not sure whether there is a possibility of both handing an exception for the UI thread, but I suspect that can happen. That is why they both have e.handled = true at the end - that should prevent it from being handled twice.
      singulars
      1. PO
      1. USKyle
 

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