From 68fa22ba9bcf0fe251e13980e6d32d68ea39e80a Mon Sep 17 00:00:00 2001 From: Vincent Baaij Date: Wed, 9 Sep 2015 15:56:00 +0200 Subject: [PATCH] Update UmbracoApplicationBase.cs There were two (almost identical) unhandled exception handlers in the code. Think it was caused by merge conflict --- src/Umbraco.Core/UmbracoApplicationBase.cs | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/src/Umbraco.Core/UmbracoApplicationBase.cs b/src/Umbraco.Core/UmbracoApplicationBase.cs index 7418d4e5b2..5b9c8903c6 100644 --- a/src/Umbraco.Core/UmbracoApplicationBase.cs +++ b/src/Umbraco.Core/UmbracoApplicationBase.cs @@ -32,19 +32,6 @@ namespace Umbraco.Core /// internal void StartApplication(object sender, EventArgs e) { - //take care of unhandled exceptions - there is nothing we can do to - // prevent the entire w3wp process to go down but at least we can try - // and log the exception - AppDomain.CurrentDomain.UnhandledException += (_, args) => - { - var exception = (Exception) args.ExceptionObject; - var isTerminating = args.IsTerminating; // always true? - - var msg = "Unhandled exception in AppDomain"; - if (isTerminating) msg += " (terminating)"; - Logger.Error(typeof(UmbracoApplicationBase), msg, exception); - }; - //take care of unhandled exceptions - there is nothing we can do to // prevent the entire w3wp process to go down but at least we can try // and log the exception