[Mono-bugs] [Bug 74901][Nor] Changed - System.Timers.Timer doesn't work properly when using the SynchronizingObject property

[bugzilla-daemon@bugzilla.ximian.com]

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 peter@novonyx.com.

http://bugzilla.ximian.com/show_bug.cgi?id=74901

--- shadow/74901	2005-05-10 16:21:23.000000000 -0400
+++ shadow/74901.tmp.28417	2005-05-11 20:01:13.000000000 -0400
@@ -1,16 +1,16 @@
 Bug#: 74901
 Product: Mono: Class Libraries
 Version: 1.1
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
-Component: System
+Component: Windows.Forms
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: sebastien@ximian.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
@@ -114,6 +114,17 @@
 Always
 
 
 Additional Information:
 Some debugging code inside corlib shows that AsyncResult are being
 allocated at each interval. However the callback isn't executed.
+
+------- Additional Comments From peter@novonyx.com  2005-05-11 20:01 -------
+This is due to the message loop not being run in the app. MWF's async 
+mechanism utilizes the message loop to send it's notifications.
+
+Placing a Application.Run() at the end of the app (before the Sleep 
+call) will show that.
+
+Not sure if we can/will fix this, or how to. Reassigning to SWF, 
+leaving open for now.
+