.NET 4.5 WinFormsSynchronizationContext changes

Answered .NET 4.5 WinFormsSynchronizationContext changes

  • Thursday, August 16, 2012 2:39 PM
     
     

    At the breaking change notes for .NET 4.5 there is following entry for the SynchronizationContext.Current property. Quote:

    Change: In the .NET Framework 4.5, Windows Forms no longer overrides a null synchronization context.
    Impact: This change may break an application that assumes that the synchronization context is always non-null.

    Does anyone know details about this change? Making a new 4.5 WinForms app still sets the SynchronizationContext when a Control subclass constructor is called, so I'm clueless about what this "breaking change" means. I'm worried about this because we are using SynchronizationContext extensively and I need to evaluate the impact of running on .NET 4.5 (especially since its not an option to run on 4.0 if the end user has 4.5 installed).

All Replies

  • Monday, August 20, 2012 9:41 AM
    Moderator
     
     

    Hi Tobias,

    I will invoke other engineer in this issue.

    Best Regards,


    Bob Wu [MSFT]
    MSDN Community Support | Feedback to us

  • Monday, August 27, 2012 5:09 PM
    Owner
     
     Answered

    Please disregard this breaking change.  It was actually reverted back to the 4.0 behavior prior to release but wasn’t removed from the list.  I have submitted a request to remove it from the MSDN document which should happen in a few weeks.


    Trevor Hancock (Microsoft)
    Please remember to "Mark As Answer" the replies that help.

  • Monday, August 27, 2012 8:14 PM
     
     
    Thank you for your answer !