If you’re developer who use Microsoft Exchange Web Services to develop client applications, then this is for you to download and play around with it. The Microsoft Exchange Web Services (EWS) Managed API 1.0 Beta provides a managed interface for developing client applications that use Exchange Web Services. The EWS Managed API simplifies the implementation of applications that communicate with Microsoft Exchange Server 2007 Service Pack 1 (SP1) and later versions of Microsoft Exchange. Built on the

With the continuation of the previous blogpost , today we’re going to see how we can use Microsoft Office Outlook Web Access or the Exchange Management Shell to configure language settings for Outlook Web Access in Microsoft Exchange Server 2007. Microsoft have provided various options to customize the OWA pages, contents/images/themes in a simpler way. As a part of that, we cam make sure that we can do the language setting for OWA, which determines the language of the Outlook Web Access logon page

As you know Collaboration Data Objects for Exchange Management or CDOEXM is used to create applications that manage Exchange servers, databases, public folders, and user mailboxes. It provides the fundamental Component Object Model (COM) classes and interfaces that are used to manage the Exchange store. From Exchange 2007 onwards… From Exchange Server 2007 onwards you can’t use the CDOEXM functionalities, because Exchange Server 2007 doesn’t include CDOEXM i.e., CDOEXM does not ship in and is not

When you migrated from Microsoft Exchange 2000 & 2003, where they provide several API's that are not included in Microsoft Exchange Server 2007. Please find the following API's that are not included in the Exchange Server 2007 environment & the recommended technologies to migrate to. APIs that are not included in Exchange 2007 API Status in Exchange 2007 Replacement Technology CDOEX De-emphasized but still supported. Exchange Web Services CDOEXM Not included in Exchange 2007. Microsoft Windows

As described in the MSDN article , Microsoft Office Outlook exports the following definitions, data structures, functions, and interfaces that were originally designed for internal use but are now exposed for public consumption. Definitions: Constants for Exported Outlook APIs Data structures: CONTAB_ENTRYID, RTF_WCSINFO, RTF_WCSRETINFO, TZDEFINITION, TZREG, TZRULE Functions: GetDefCachedMode, GetDefCachedModeDownloadPubFoldFavs, HrCreateApptRebaser, HrGetAutoDiscoverXML, MAPICrashRecovery, RebaseTaskComplete,

Do you know the support that is available for applications that use the Web Distributed Authoring and Versioning (WebDAV) protocol to access Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003 ?   What is supported? Microsoft support the use of the WebDAV protocol for the following items: •Non-recurring appointments •Contacts in Microsoft Outlook that you create or modify •Folders that you create in Outlook and in Exchange 2000 Server or Exchange Server 2003 •E-mail

MailMsg - COM Class The MailMsg COM class represents a message as it proceeds through the SMTP service. The information within the MailMsg object is persisted to some physical location such as the file system using objects and file handles provided by the installed store driver object. The MailMsg COM class is integral to the SMTP service and does not need to be implemented. Transport and protocol event sinks use references to a MailMsg object to access information about the message and the message

The support guidelines for client-side messaging development This is one of the finest article describes "what is supported" and "what is not supported" when you develop custom solutions that integrate with Microsoft-based messaging products or Microsoft technologies. This article also contains most of the key information to be aware of when you develop with Microsoft products and Microsoft technologies. However, this article does not cover all scenarios. Some of them were, Integrating with Outlook

Hi Exchange and Outlook developers!! I found this wonderful article , which describes a change in how Microsoft Office Outlook 2003 Service Pack 2 (SP2) and later service packs, Microsoft Exchange Server 2003 Service Pack 2 (SP2), and later versions of Exchange Server and of Outlook handle meetings. This new design addresses disappearing-meeting scenarios that were introduced by Outlook 2003 in cached mode. The new design does not have a visible effect on end-users . However, the new design can affect

Migrating from Exchange 2000 and Exchange 2003 APIs I found the following article, which will help to users who want to migrate from Exchange Server 2000 and 2003 APIs to Exchange Server 2007. This article talks about Exchange 2000 Server and 2003 based several APIs that are not included in Microsoft Exchange Server 2007. Also this article talks about the recommended technologies that are recommended to migrate to.