What’s New in the Exchange 2010 Web Services SDK
Last modified: June 28, 2013
Applies to: Exchange Server 2007 | Exchange Server 2010
In this article
New Content
Clarifications and Fixes
Other Small Changes
This topic summarizes the changes that have been made to this release of the Exchange Server 2010 Web Services Software Development Kit (SDK).
New Content
The topics listed in this section are new or contain information that is new to this release of the Exchange 2010 Web Services SDK.
The following operation topic has been added:
The following operation topics have been updated:
ConvertId Operation — Updated to reflect that impersonation is now supported for identifier conversion, and to include a SOAP header section.
FindItem Operation — Updated to reflect that the DateTimePrecision element is supported in the SOAP header.
GetItem Operation — Updated to include a SOAP headers section.
GetUserAvailability Operation — Updated to include new SOAP headers.
The following XML element topics have been added:
The following XML element topics have been updated:
Contact — Updated to include new child elements.
RequestServerVersion — Updated to include the "Exchange2010_SP2" version value.
ResponseCode — Updated to include the "ErrorAttachmentNestLevelLimitExceeded" value.
ResolveNames — Updated to include the ContactDataShape attribute.
ResponseMessages — Updated to include the GetPasswordExpirationDateResponse element.
The FieldURI element topic has been updated to include the following property identifiers:
item:StoreEntryId
contacts:Alias
contacts:DirectoryId
contacts:DirectReports
contacts:ManagerMailbox
contacts:MSExchangeCertificate
contacts:notes
contacts:PhoneticFullName
contacts:PhoneticFirstName
contacts:PhoneticLastName
contacts:Photo
The following types and their members have been added:
The following members have been added to the AlternateIdType type:
The following members have been added to the ContactItemType type:
The "NoForward" value has been added to the DeliverMeetingRequestsType enumeration.
The following members have been added to the ExchangeServiceBinding type:
BeginGetPasswordExpirationDate(GetPasswordExpirationDateType, AsyncCallback, Object)
GetPasswordExpirationDateAsync(GetPasswordExpirationDateType, Object)
GetPasswordExpirationDateAsync(GetPasswordExpirationDateType)
The "Exchange2010_SP1" and "Exchange2010_SP2" values have been added to the ExchangeVersionType enumeration.
The "OtherError" and "RecipientOrganizationFederatedWithUnknownTokenIssuer" values have been added to the InvalidRecipientResponseCodeType enumeration.
The "GetPasswordExpirationDateResponse" and "FindMailboxStatisticsByKeywordsResponseMessage" values have been added to the ItemsChoiceType4 enumeration.
The StoreEntryId member has been added to the ItemType type.
The ContactDataShape and ContactDataShapeSpecified members have been added to the ResolveNamesType type.
The "ErrorAttachmentNestLevelLimitExceeded" value has been added to the ResponseCodeType enumeration.
The following values have been added to the UnindexedFieldURIType enumeration:
contactsDirectoryId
contactsPhoto
contactsNotes
contactsMSExchangeCertificate
contactsManagerMailbox
contactsPhoneticFullName
contactsPhoneticFirstName
contactsPhoneticLastName
contactsUserSMIMECertificate
itemStoreEntryId
contactsDirectReports
contactsAlias
The IsAssociated and IsAssociatedSpecified members have been added to the UploadItemType type.
Clarifications and Fixes
The topics listed in this section were changed to correct errors, and to make confusing sections more clear. A big "thank you" to the customers and developers who used the Exchange Server 2010 SDK Feedback alias (exsdkfb@microsoft.com) to inform us of these problems. You can always send us feedback by using the feedback section that appears at the bottom of every page in the downloadable SDK.
The GetUserAvailability Operation operation and the FreeBusyViewType element topics have been updated to clarify the free/busy information that is returned for a distribution list.
Other Small Changes
Other small changes were made to fix links, code examples, and so on. Again we thank our customers and developers who identified and informed us of these problems.