This is a question that we hear frequently since we have released Exchange 2007. And our answer has to be heard loud and clear: going forward Exchange Web Services should be the API of choice for...
Updated Jul 01, 2019
Version 2.0
Blog Post
I'm going to try to answer a couple of post questions here.
Chris, Outlook is using Exchange Web Services today for Availability Service, OOF, and AutoDiscover functionality.
Nate, we would love the MAPI developers out there to give us feedback on what you are currently doing in MAPI that you can't do in EWS. It is true we do not have a separate API for GAL, but we do expose the most important GAL functionality (ResolveNames/ExpandDL).
ResolveNames will retrieve detailed GAL information about a user, similar to the old GalFind OWA URL. You can use EWS to access embedded messages.
Karsten, you could use Exchange Web Services to register for a new mail notification on a public folder (coming soon in SP1) and then asynchronously change the message type. However, I would recommend using the Transport APIs for this functionality since they will fire before the item even gets delivered to the folder and will be more efficient in this specific scenario.
Uli, CDOEXM is not supported in Exchange 2007, you will need to use the Exchange PowerShell.
Stanley, you will need a domain account of some sort, either computer or user account to access Exchange Web Services.
Arthur, I understand your sentiments, and our goal with Exchange Web Services is to create an API that does not require you to "straddle" multiple APIs. EWS may not do 100% of what each of those individual APIs did in Exchange 2007, but as we are showing in SP1 we are committed to making sure that we understand and address the gaps (by cateloging at an API by API level as you suggest by the way) that are important to our developers. You can help us out with this effort by putting your vote in for the functionality you'd like to see added in Exchange Web Services. Post your request on the blog, or in our TechCenter newsgroup:http://msdn2.microsoft.com/en-us/exchange/default.aspx
Rob,
Yep, you'll need to use Powershell instead of CDOEXM to connect to Exchange 2007.
Chris, Outlook is using Exchange Web Services today for Availability Service, OOF, and AutoDiscover functionality.
Nate, we would love the MAPI developers out there to give us feedback on what you are currently doing in MAPI that you can't do in EWS. It is true we do not have a separate API for GAL, but we do expose the most important GAL functionality (ResolveNames/ExpandDL).
ResolveNames will retrieve detailed GAL information about a user, similar to the old GalFind OWA URL. You can use EWS to access embedded messages.
Karsten, you could use Exchange Web Services to register for a new mail notification on a public folder (coming soon in SP1) and then asynchronously change the message type. However, I would recommend using the Transport APIs for this functionality since they will fire before the item even gets delivered to the folder and will be more efficient in this specific scenario.
Uli, CDOEXM is not supported in Exchange 2007, you will need to use the Exchange PowerShell.
Stanley, you will need a domain account of some sort, either computer or user account to access Exchange Web Services.
Arthur, I understand your sentiments, and our goal with Exchange Web Services is to create an API that does not require you to "straddle" multiple APIs. EWS may not do 100% of what each of those individual APIs did in Exchange 2007, but as we are showing in SP1 we are committed to making sure that we understand and address the gaps (by cateloging at an API by API level as you suggest by the way) that are important to our developers. You can help us out with this effort by putting your vote in for the functionality you'd like to see added in Exchange Web Services. Post your request on the blog, or in our TechCenter newsgroup:http://msdn2.microsoft.com/en-us/exchange/default.aspx
Rob,
Yep, you'll need to use Powershell instead of CDOEXM to connect to Exchange 2007.