[Mono-bugs] [Bug 78139][Nor] Changed - Bad implementation of SynchronizationContext.Post()

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Apr 19 07:25:14 EDT 2006


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 flipper98 at gmx.net.

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

--- shadow/78139	2006-04-19 04:52:02.000000000 -0400
+++ shadow/78139.tmp.27599	2006-04-19 07:25:14.000000000 -0400
@@ -39,6 +39,14 @@
 What is similarly important is that SynchronizationContext.Post() does
 not seem to run the callback synchronously (Post() itself should
 return asynchronously but the callback execution should be synchronous).
 
 It affects on System.ComponentModel.BackgroundWorker behavior. (I also
 doubt this problem goes away by using ThreadPool.QueueUserWorkItem()).
+
+------- Additional Comments From flipper98 at gmx.net  2006-04-19 07:25 -------
+It affects on every class that implements the event-based asynchronous
+pattern, which makes use of the AsyncOperation class which in turn
+uses the SynchronizationContext class. (see 
+http://msdn2.microsoft.com/en-us/library/hkasytyf(VS.80).aspx).
+I'm currently implementing this pattern in one of my apps classes,
+this is why i stumbled over this problem.


More information about the mono-bugs mailing list