Forever learning new stuff it seems NetworkCredential is not part of the Independentsoft API. I could use the CredentialCache..::.DefaultNetworkCredentials or the CredentialCache..::.DefaultCredentials Property. http://msdn.microsoft.com/en-us/library/system.net.credentialcache.defaultcredentials.aspx To get the logged in users credentials.
I hope this is right. Regards Peter Maddin Applications Development Officer PathWest Laboratory Medicine WA Phone : +618 9473 3944 Fax : +618 9473 3982 E-Mail : [email protected] The contents of this e-mail transmission outside of the WAGHS network are intended solely for the named recipient's), may be confidential, and may be privileged or otherwise protected from disclosure in the public interest. The use, reproduction, disclosure or distribution of the contents of this e-mail transmission by any person other than the named recipient(s) is prohibited. If you are not a named recipient please notify the sender immediately. From: [email protected] [mailto:[email protected]] On Behalf Of Maddin, Peter Sent: Wednesday, 17 February 2010 12:22 PM To: ausDotNet Subject: RE: Exchange Web Services Development Thanks I will be investing in the Exhange server text. It costs $118 but I have a coupon somewhere so I try and find that before I purchase it. Also there is a good API from Independentsoft but their examples require one to get a Network credential using a users account and password <snip> NetworkCredential credential = new NetworkCredential("username", "password"); Service service = new Service("https://myserver/ews/Exchange.asmx";, credential); </snip> There may be a way to get the network credentials of the currently logged in user. I am still investigating that. If one has to obtain user credentials each time (or cache them) then I am not much better off than using SMTP (although Ken says one can make this transparent by changing the SMTP connector) Regards Peter Maddin Applications Development Officer PathWest Laboratory Medicine WA Phone : +618 9473 3944 Fax : +618 9473 3982 E-Mail : [email protected] The contents of this e-mail transmission outside of the WAGHS network are intended solely for the named recipient's), may be confidential, and may be privileged or otherwise protected from disclosure in the public interest. The use, reproduction, disclosure or distribution of the contents of this e-mail transmission by any person other than the named recipient(s) is prohibited. If you are not a named recipient please notify the sender immediately. From: [email protected] [mailto:[email protected]] On Behalf Of David Connors Sent: Wednesday, 17 February 2010 11:54 AM To: ausDotNet Subject: Re: Exchange Web Services Development On 17 February 2010 12:53, Maddin, Peter <[email protected]<mailto:[email protected]>> wrote: I tried a trial MAPI control which is ok. Integrated security is fine. An issue which becomes all to apparent is those annoying security dialogs that keep popping up and which gives one the whoops (not to mention the users who will crucify me if I foist this on them). I suspect that one also has to install Outlook to gain access to the appropriate mapi dll. If one could avoid this it would be great. Are you talking about the warnings from Outlook about "Application XYZ trying to access your contacts, Allow for 1 Minute" etc? No way around them aside from reconfiguring Outlook AFAIK - Tools -> Trust Centre -> Programmatic Access. You can change Outlook to never warn about programmatic access but then that is for all apps on your system and not a good idea for security. MAPI is a fundamentally retarded and needlessly complex (MSRPC based) way to access mail. Unless you need to do specific stuff to do with the information store on exchange, etc, I'd recommend you just stick with something standards based. You'll avoid all the nonsense such as calls failing because Outlook has a modal dialogue box open etc. I would like to try out the new web services that are available. I have a link to http://msdn.microsoft.com/en-us/library/dd877037.aspx They're pretty good and very functional AFAIK and hopefully one day they will kill MAPI in favour of them. If you have a Mac running OSX Snow Leopard, all of the native apps (mail, contacts and calendar) directly sync against Exchange using those web services - which is pretty cool I think! My only gripe is why they are needed in light of activesync (MSRPC+MAPI vs ActiveSync vs Web Services ALL to access the one product?!?!) [ ... ] -- David Connors ([email protected]<mailto:[email protected]>) Software Engineer Codify Pty Ltd - www.codify.com<http://www.codify.com> Phone: +61 (7) 3210 6268 | Facsimile: +61 (7) 3210 6269 | Mobile: +61 417 189 363 V-Card: https://www.codify.com/cards/davidconnors Address Info: https://www.codify.com/contact
