A colleague of mine claims that EWS is "legacy" and that we should use other ways of programming for Exchange. I agree that asmx services are "legacy" but I have found no indication that Microsoft intends to give up on EWS with the improvements to EWS in Exchange 2010 and the publication of the EWS Managed API.

Is it safe to continue using EWS?

  • Can your colleague cite an official source? I find it hard to believe something relatively new is being considered legacy. Things aren't legacy unless they're replaced by something, and off the top of my head I can't think of anything. – Ben Pilbrow Mar 24 '11 at 13:30
  • @Ben Pilbrow: I feel the same way that you do and he has not been able to come up with any liable source. – Jakob Christensen Mar 24 '11 at 13:35
  • The way MS has been pushing EWS, I think it might be the long term replacement for MAPI. – Joe Doyle Mar 24 '11 at 13:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.