Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=77208 --- shadow/77208 2006-01-10 23:09:27.000000000 -0500 +++ shadow/77208.tmp.11596 2006-01-10 23:09:27.000000000 -0500 @@ -0,0 +1,27 @@ +Bug#: 77208 +Product: Mono: Class Libraries +Version: 1.1 +OS: +OS Details: +Status: NEW +Resolution: +Severity: +Priority: Normal +Component: System +AssignedTo: [EMAIL PROTECTED] +ReportedBy: [EMAIL PROTECTED] +QAContact: [EMAIL PROTECTED] +TargetMilestone: --- +URL: +Cc: +Summary: in MS.Net 2.0, finally blocks are not interrupted by ThreadAbortExceptions + +In MS. Net 1.1 and Mono, if an Abort is received by a thread which is +currently in a finally block, the finally block is interrupted. This is +documented in the Abort method section on msdn: + +http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemthreadingthreadclassaborttopic1.asp + +However, this behavior has changed in MS .Net 2.0. A finally block is not +interrupted. Instead the exception is delayed until the end of the finally +block. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
