Questions tagged [exchangewebservices]

Welcome to the EWS tag on StackOverflow!!! Use this tag to find answers, ask questions, and answer questions about the Exchange Web Services (EWS) and the Autodiscover web services provided by Exchange Server and Exchange Online. To help you create higher quality and more consistent posts, here is some guidance on how to title and flesh out the post body so that the community can more easily answer your questions:

Post Title

The post title is the first thing a reader will see. To give the reader an idea about what the post will contain, we suggest you use the following format:

Exchange Version - Programming Language - Client platform: Information you seek

Here are a couple of example titles:

• E2013 - Java - Android KitKat: How do I upload more than one contact?
• EXO - C# - Windows 8.1: Can I use the EWS Managed API with a Windows Store App?

Post Body

The post body should provide as much background information as possible to help the other contributors answer your questions. The following list identifies information you should consider providing when creating your post (of course, do not post sensitive information like account names, passwords, machine names, etc):

• Exchange Version: Exchange version and service pack. Include build and version numbers if available. You can get the build and version from the XML response.
• Client API version: Provide the client API version, if applicable.
• IDE: The development tools you are using if they are applicable to answering your question.
• Targeted features: Identify which features are involved in your question.
• Code examples: Provide both the client code, and for debugging purposes, the XML request and response sent and received by the client. You can use applications like Fiddler or NetMon to capture the request/response XML. If you are using the EWS Managed API, you can provide an XML trace, here's how.
• Scenario description: Describe the scenario that results in you posting a question to this forum. More information is better.

Here are some considerations for describing your scenario:

• Give a thorough description of what you are trying to do and how you are attempting to do it. Provide the steps you have already attempted.
• Identify resources you've tried to use (include links)
• Identify the target platforms
• Provide a code example that describes the problem (as long as it does not reveal sensitive information.)
• Give a description of the environment for client and server hardware and software. Firewalls, proxy, trusts, security models, system architecture and other environmental factors can have programmability implications.
• Provide error codes and exceptions; identify the specific part of the code that threw an exception. Provide stack traces if applicable.
• Provide log entries and traces as long as they do not reveal sensitive information. Delete sensitive information.
• Provide performance counter information from the Exchange Server.
• List the specific questions that you want answered.
• Don't assume that the reader knows all the background information. The more information that you provide, the better/quicker answer you will receive. It is easy to skip content that is understood; that is much better than leaving out information.

Mark answers

This forum has mechanisms for marking and qualifying answers as useful. When a question has been successfully answered, please mark the answer as useful so that readers can easily scan posts for the answer.