Support policy statement for Microsoft Graph

As new versions of the Microsoft Graph REST APIs and Microsoft Graph SDKs are released, earlier versions will be retired. Microsoft will declare a version as deprecated at least 24 months in advance of retiring an API or an SDK. So Microsoft Graph too follows the Microsoft Lifecycle Policy. When we increment the major version…

1

MAPI Developer: API elements deprecated in Outlook 2013

Are you an MAPI developer? Then, this article is targetted for you. The API elements (like, IXPLogon::RegisterOptions, OPTIONDATA, OPTIONCALLBACK, IMAPISession::MessageOptions, IMAPISession::QueryDefaultMessageOpt, IAddrBook::RecipOptions, IAddrBook::QueryDefaultRecipOpt)  are deprecated in Microsoft Outlook 2013. They are no longer supported and you should not use them in new projects. These API elements are deprecated in this release because of obsolete message…


What you mean by Recommended vs. Supported vs. Deprecated vs. Deemphasized?

When we talk to customers they want to know what is the difference between Recommended, Supported, Deprecated and deemphasized means. This is already well explained in Patrick’s what unsupported mean article. In simple terms, “Recommended vs. Supported” means, Supported usually means well tested Support statements define strict boundaries Recommendations define the “best case” or the…


Developer : Does Exchange Client Extension (ECE) deprecation matters me?

Per Randy’s blog post, Exchange Client Extension (ECEs) deprecation does (for Outlook 2010) matters the developers. For more information please refer the excerpts of the blog post: “For most Outlook users, this announcement will not concern you. However, if you are a developer that uses Exchange Client Extension interfaces to build a solution in Outlook,…