About: VSTO for Outlook

API Type:  UI Customization API Interface: .NET Business Logic: Adds features to the Outlook UI and to Outlook processing. Development Languages: .NET, OOM. Property Access: Yes Product Versions: Visual Studio 2005 and later, Office 2003 and later. Summary: Outlook VSTO add-in development allows you to write add-inapplications which will run in Outlook from Office. Points…

0

Building messaging applications with “Any CPU”

When building pure .NET applications doing builds using Any CPU usually go pretty smoothly. Even when mixing in some COM objects things usually go well. However, developers often run into issues with .NET code using COM objects then deploying their applications to other computers where the bitness of their development box OS does not match…

0

About: Messaging APIs

There are many different types of APIs which are focused on mailbox access, administration and care.  There are different ways to approach APIs when looking for one to use for your messaging project.  This article categorizes APIs by type.  Knowing the type of application is needed at the start will help guide you to picking…

0

About: Mail Apps for Outlook

API Type:  UI Customization API Interface: .NET Business Logic: Adds features to standard item forms. Development Languages: .NET Property Access: Yes Product Versions: 2013, 2016, Exchange Online.  Summary Mail Apps for Outlook development allows you to write one application which will run in Outlook desktop, OWA Web APP and OWA for Devices.  The type of…

0

About: Exchange VSS Writer – Exchange backup and restore

API Interface: COM Library  (IUnknown only) Business Logic: Exchange Backup. Language Support: Unmanaged C++, .NET. Direct Property Access: N/A. Product Versions: Exchange 2003 and later.      Summary: The Volume Shadow Copy Service for Windows provides a facility for applications to backup and restore data within another application or Windows.  It’s a COM based API that allows developers to…

0

Exchange and Outlook Development Help

I’ve assembled lists of sites where you can look for information and help on APIs dealing with developing applications against Exchange and Outlook. Messaging Development training: Exchange Server development https://msdn.microsoft.com/en-us/library/office/dn820100 Welcome to the Outlook 2013 developer reference https://msdn.microsoft.com/en-us/library/office/ee861520.aspx Channel 9 https://channel9.msdn.com/ This is Microsoft’s video based training site.  It covers a broad range of developer…

0

About: Extended MAPI

API Type: Mailbox Accessor API Interface: COM-like but not true COM.  MAPI pre-dates COM. Business Logic: Messages and AddressBook, etc. Language Support: Unmanaged C++ only. Direct Property Access: Yes. Product Versions: All versions of Outlook and Exchange versions up to 2003.  Also available for download. Summary: MAPI is the root level API and architecture for the Outlook…

0

Best Practices – What is supported and not.

The issue of supportability comes up a lot.  I would like cover it in this blog post. When we get cases from customers we look at the servers, software and APIs involved.  In addition, the development scenarios and configurations are taken into considerations. A lot of customers run outdated versions of Exchange and Outlook – such as…

0

EWS Best Practices

If your a new developer to EWS or are looking at implementing best practices in development going forward, you should be aware of at least some of the common areas where developers have issues. There are a number of things which should be understood while writing EWS code and sometimes developers miss certain aspect of…

0

EWS Best Practices – Searching

Remember that your application is not the only one going against the server, so play nice.  You may be able to get needed performance in your application but when other applications are going against the server in the real world you may find that the overall experience for all users on that server are poor. …

0