SynchronizationContext.Current is null

Add-in Express™ Support Service
That's what is more important than anything else

SynchronizationContext.Current is null
Kiru Marimuthu

Posts: 38
Joined: 2017-07-20
Adding to my above question about inconsistent in SynchronisationContext behavior in different machines. Now I have different behavior on my machine.

I got a test project where the SynchronizationContext.Current is null in the constructor of the AddinModule.cs. But my actual project it is not null.

public AddinModule()
            Context = SynchronizationContext.Current;

It will be appreciated if you could let us know the right place where the SynchronizationContext.Current can be assigned consistently.
I got a test project, please let me know how could I attach to this question.
Posted 05 Oct, 2017 04:45:30 Top
Andrei Smolin

Add-in Express team

Posts: 16080
Joined: 2006-05-11
Hello Kiru,

Please check my response to your other question at

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 05 Oct, 2017 04:50:36 Top