Robert Jordan wrote: > How about relying on System.Threading.SynchronizationContext.Current? > This could work w/out exposing any internal calls/env vars. This is actually a pretty good idea, but you'd need to capture the SynchronizationContext in the __ComObject constructor, not use the one of the finalization thread. Regards, Jeroen