StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Just read your thread, cause I experience the same with a webrole. Now I added your code snippet and check if I will experience this error again. Did some research about the AppDomain class: <a href="http://msdn.microsoft.com/en-us/library/system.appdomain.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/system.appdomain.aspx</a>. As a matter of fact I was searching for the unhandled exception policy but have not found it. But I found the event "UnhandledException" <a href="http://msdn.microsoft.com/en-us/library/system.appdomain.unhandledexception.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/system.appdomain.unhandledexception.aspx</a>. </p> <p>But you wrote this doesnot work. Cause this will hit me later on as well - I will run a 3rd party open source component in an azure worker role - I did some research.</p> <p>I will try to create a new AppDomain for the 3rd pary code - and if an exception occurs, it will crash/unload the newly created AppDomain and not the current I run the code in. Another solution would probably be creating a new process, which is I suppose more work.</p> <p>EDIT: I revisited this topic: in version 2.0 it was introduced to tear down the application domain in case a thread (not main thread) experience an error in a class library. It seems that even a seperate ApplicationDomain will not help. As I understood this design should help debugging errors hidden in libraries by catch exceptions on library level and handle them appropriately. But what irritates me - what happens if we use 3rd party class libraries we have no control of? Then it seems we are stuck if our issue is to small for the vendor to resolve it in time necessary for us.</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