Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would handle the exceptions in the remote application domain. First I would create a new assembly with the exception handling code and then I would load it into child application domain.</p> <p>The following code should give some ideas.</p> <pre><code>class Program { private class NonSerializableException : Exception { } static void Main(string[] args) { var childAppDomain = AppDomain.CreateDomain("Child"); Console.WriteLine("Created child AppDomain #{0}.", childAppDomain.Id); // I did not create a new assembly for the helper class because I am lazy :) var helperAssemblyLocation = typeof(AppDomainHelper).Assembly.Location; var helper = (AppDomainHelper)childAppDomain.CreateInstanceFromAndUnwrap( helperAssemblyLocation, typeof(AppDomainHelper).FullName); helper.Initialize(UnloadHelper.Instance); childAppDomain.DoCallBack( () =&gt; new Thread(delegate() { throw new NonSerializableException(); }).Start()); Console.ReadLine(); } private sealed class UnloadHelper : MarshalByRefObject, IAppDomainUnloader { public static readonly UnloadHelper Instance = new UnloadHelper(); private UnloadHelper() { } public override object InitializeLifetimeService() { return null; } public void RequestUnload(int id) { // Add application domain identified by id into unload queue. Console.WriteLine("AppDomain #{0} requests unload.", id); } } } // These two types could be in another helper assembly public interface IAppDomainUnloader { void RequestUnload(int id); } public sealed class AppDomainHelper : MarshalByRefObject { public void Initialize(IAppDomainUnloader unloader) { AppDomain.CurrentDomain.UnhandledException += (sender, e) =&gt; unloader.RequestUnload(AppDomain.CurrentDomain.Id); } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PODealing with non-serializable unhandled exceptions from a child AppDomain
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmgronber
    1. USmgronber
    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
    1. COThanks mgronber, but even with this solution the NonSerializableException still gets propagated to the parent AppDomain as an unhandled SerializationException. I can't identify the SerializationException as comming from a child AppDomain, which is forcing me to either ignore it or treat it as any other unhandled exception and terminate the application.
      singulars
      1. PO
      1. USJames Thurley
    2. COJust to add, we actually use a similar technique to what you're proposing for handling the Dispatcher.UnhandledException events... it works nicely there because you can mark the exception as handled and it won't propagate further. AppDomain.UnhandledException sadly doesn't support this and always bubbles the exception up to the main AppDomain :(
      singulars
      1. PO
      1. USJames Thurley
    3. COHow do you execute the code in the child domain? Could you use a helper method that calls the code and catches any exceptions that are left unhandled?
      singulars
      1. PO
      1. USmgronber
 

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