> Hi,
>
> Sorry for letting you wait.
>
> I finally found out the root cause. The OnStop method of ServiceBase is
> triggerred by ServiceBase.DeferredStop method. Using Reflector, we can see
> the source code like this:
>
> private unsafe void DeferredStop()
> {
>       fixed (NativeMethods.SERVICE_STATUS* service_statusRef1 =
> &this.status)
>       {
>             int num1 = this.status.currentState;
>             this.status.checkPoint = 0;
>             this.status.waitHint = 0;
>             this.status.currentState = 3;
>             NativeMethods.SetServiceStatus(this.statusHandle,
> service_statusRef1);
>             try
>             {
>                   this.OnStop();
>                   this.WriteEventLogEntry(Res.GetString("StopSuccessful"));
>                   this.status.currentState = 1;
>                   NativeMethods.SetServiceStatus(this.statusHandle,
> service_statusRef1);
>             }
>             catch (StackOverflowException)
>             {
>                   throw;
>             }
>             catch (OutOfMemoryException)
>             {
>                   throw;
>             }
>             catch (ThreadAbortException)
>             {
>                   throw;
>             }
>             catch (Exception exception1)
>             {
>                   this.WriteEventLogEntry(Res.GetString("StopFailed", new
> object[] { exception1.ToString() }), EventLogEntryType.Error);
>                   this.status.currentState = num1;
>             }
>       }
> }
> As you can see, the DeferredStop method catched all the exceptions, so the
> exception in the OnStop method will not trigger our
> AppDomain.UnhandledException event. So was DeferredPause for OnPause
> method.
>
> Hope this helps.
>
> Best regards,
> Jeffrey Tan
> Microsoft Online Community Support
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

> Hi,
>
> I assume you are using System.Timers.Timer component. In this component,
> Timer.Elapsed event is triggered by System.Timers.Timer.MyTimerCallback
> method. It is this method that catches all the exceptions, below is the
> source code comes from Reflector:
>
> private void MyTimerCallback(object state)
> {
>       if (state == this.cookie)
>       {
>             if (!this.autoReset)
>             {
>                   this.enabled = false;
>             }
>             Timer.FILE_TIME file_time1 = new Timer.FILE_TIME();
>             Timer.GetSystemTimeAsFileTime(ref file_time1);
>             ElapsedEventArgs args1 = new
> ElapsedEventArgs(file_time1.ftTimeLow, file_time1.ftTimeHigh);
>             try
>             {
>                   if (this.onIntervalElapsed != null)
>                   {
>                         if ((this.SynchronizingObject != null) &&
> this.SynchronizingObject.InvokeRequired)
>                         {
>                              
> this.SynchronizingObject.BeginInvoke(this.onIntervalElapsed, new object[] {
> this, args1 });
>                         }
>                         else
>                         {
>                               this.onIntervalElapsed(this, args1);
>                         }
>                   }
>             }
>             catch (Exception)
>             {
>             }
>       }
> }
> So AppDomain.UnhandledException is not fired at all.
>
> Hope this helps.
>
> Best regards,
> Jeffrey Tan
> Microsoft Online Community Support
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>