[Mono-bugs] [Bug 328006] New: [Patch] AsyncOperationManager: SyncContext needs to be tied to SyncContext.Current

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=328006#c327608

           Summary: [Patch] AsyncOperationManager: SyncContext needs to be
                    tied to SyncContext.Current
           Product: Mono: Class Libraries
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: System
        AssignedTo: mono-bugs at ximian.com
        ReportedBy: jpobst at novell.com
         QAContact: mono-bugs at ximian.com
            Blocks: 327608
          Found By: ---


Created an attachment (id=174469)
 --> (https://bugzilla.novell.com/attachment.cgi?id=174469)
Unit Test

While working on bug #327608, I came across two changes needed.

The first is SynchronizationContext.SetSynchronizationContext is not
implemented.  The second is that AsyncOperationManager needs to use
SynchronizationContext.Current instead of maintaining its own SyncContext. 
(This is used by the BackgroundWorker to use the correct SyncContext.)

Some background is available as the last question on:
http://msdn.microsoft.com/msdnmag/issues/06/06/NETMatters/default.aspx.

I will attach the tests that show this behavior, and the patch to fix it.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.