Best Practices: EWS Managed API coding for Exchange

There are issues which we seem to get a lot of cases on which are tied to the way a customer writes their code.  Often there are sections of code which were missing or that they otherwise should have implemented.  If your running into an issue or writing new code, then please read all points…

0

Wait! Before you use that sample…!!!

One of the biggest mistakes developers and admins make is to take code or a script and plug it right into production.  Any and all code from any source samples really needs to be looked at and checked to be sure it does what you expect, does not cause issues and does nothing malicious.  All samples from…

2

About: CDO for Windows 2000 (CDOSYS)

API Type: SMTP Sender. API Interface: COM Library. Business Logic: Sending mail via SMTP Language Support: Works with both managed (.NET) and unmanaged code and scripting languages such as VBScript. Direct Property Access: N/A. Product Versions: Windows 2000 and later. Summary: CDOSYS has been a system component used to send email since Windows 2000.  It was meant to replace CDONTS. …

1

Best Practices – EWS Authentication and Access Issues

Authentication and access to a mailbox is an often misunderstood area.  I’m going to cover Authentication and type of access (impersonation vs delegate access vs direct access) and common problems developers run into in this article. Authentication vs Authorization. Lets start from the beginning with some basic information on authentication and authorization,  The first thing…

3

Best Practices – Enhancing EWS

There is only one supported way to enhance EWS and that is for a customer with a Premier agreement to open a support case with Microsoft and have a Design Change Request (DCR) filed to add the needed functionality.   I’ve seen customers do a lot of unsupported things with EWS including modifying the EWS stream, running…

0

EWS Best Practices

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…

0

EWS Best Practices – Searching

Remember that your application is not the only one going against the server, so play nice.  You may be able to get needed performance in your application but when other applications are going against the server in the real world you may find that the overall experience for all users on that server are poor. …

0

EWS Best Practices – Threading issues with the EWS managed API

An instance of the service object is not safe across threads and it’s noted as such in in the documentation.  IE they are not thread safe. While this seems like a simple point there are a lot of developers who are either ignoring this, don’t understand or are not reading the documentation. ExchangeService classhttps://msdn.microsoft.com/en-us/library/microsoft.exchange.webservices.data.exchangeservice(v=exchg.80).aspx So, it’s best…

0

EWS best practices – Tracing and logging

A lot of programmers will write code for EWS thinking that the code and some knowledge of EWS is all they need to troubleshoot issues.  With even simple applications there is a need to being able to getting traces of traffic and often the ability for applications to log the traffic themselves.  Without such logs…

0

About: CDO for Windows NT (CDONTS)

API Type: SMTP Sender. API Interface: COM Library. Business Logic: Sending mail via SMTP, read mail via POP3. Language Support: Any *unmanaged* COM compatible language (C++, VB6, VB Script). Direct Property Access: N/A. Product Versions: Windows NT and Windows 2000.   Summary:   CDONTS was viewed as a subset of CDO 1.21 in Windows NT and Windows 2000.  It’s primary…

0