If your a new developer to EWS or are looking at implementing best practices in development going forward, you should be aware of at least some of the common areas where developers have issues. There are a number of things which should be understood while writing EWS code and sometimes developers miss certain aspect of development and end up designing and coding themselves into a hole – I’ve seen this happen countless times with developers who I would give an A+ rank to. So, I’ve been pulling together information on the subject and writing what content for what seems unclear or does not exist. In some of the blog posts I try to push certain points since they are critical key areas not to be slighted. I will be updating this list of articles and adding more content in the future.
About: Exchange Web Services (EWS)
EWS Schema Versions – Why can’t I pick versions for 2007 SP2/SP3 or 2010 SP3?
Best Practices – EWS Authentication and Access Issues
Exchange throttling is your friend… well, more like a police officer.
EWS Best Practices – Tracing and logging
EWS Best Practices – Threading issues with the EWS managed API
EWS Best Practices – Searching
EWS Best Practices – “AllItems” folder
EWS Streaming Notifications with Exchange 2013
EWS PUSH – What is the StatusFrequency for?
Best Practices – Enhancing EWS
Best Practices – What is supported and not.
Best Practices – EWS is not generating ATTENDEE section for iCal/MIME/VCALENDAR pulled from a meeting.
About: Messaging APIs