Hello,

I had a routine that worked fine in the main thread of an application. Then when I put that routine into a BackgroundWorker process, it errors out on the connect method. The error is below, any clues??

The call to QI for interface 'OpenNETCF.Desktop.Communication.IDccMan' with IID '{A7B88841-A812-11CF-8011-00A0C90A8F78}' failed with HRESULT 0x80004002 (No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE))). One likely reason this failed is that the object does not have a proxy/stub dll properly registered.

Anybody? I'm trying to copy over a large file and would like not to do this on the main UI thread...

I've not tried it, but my guess is that RAPI uses Windows Messages for posting status notifications internally and it doesn't like having that on a thread other than the primary UI thread.  There's no reason you can't Connect via the primary thread and then do the transfer itself in the background.