Quote Originally Posted by InvisibleDuncan View Post
Hmmm. Okay, maybe I shouldn't have asked a bunch of VB developers!

I think my only option is to save it locally on my current domain and then use impersonation (another new thing for me!) to copy it over. Does that sound sensible?
Quote Originally Posted by NeedSomeAnswers View Post
Lol there are a few of us here who do C# but EWS and exchange integration are fairly specialist, either you have done it or you haven't!

Why do you need to use Impersonation? if you save the attachments locally to you, can you not just copy them across as files to the other domain location? OR am i missing part of your requirement?
NSA - I am currently a part of one domain... I cannot simply access a resource on a different domain ... that's what the impersonation does... allows the current context to impersonate a user on a different domain. We do this in our app, although we are usually impersonating a different user on the same domain - it's a web-based app, the IISUSER doesn't always have access to certain file system resources, so the user has the ability to tell the system, hey when you access the file system, use this user instead.

Duncan - yes, impersonation is going to be likely the way to go.

-tg