Dan's WebDAV 101

This blog covers Messaging API development for Exchange and Outlook. My name is Daniel Bagley, I'm on the Messaging Developer Team.

Browse by Tags

Tagged Content List
  • Blog Post: Wait! Before you use that sample...!!!

    One of the biggest mistakes developers and admins make is to take code or a script and plug it right into production. Any and all code from any source samples really needs to be looked at and checked to be sure it does what you expect, does not cause issues and does nothing malicious. All samples from...
  • Blog Post: About: Exchange Transport Agents

    API Interface: .NET and in process with Exchange transport. Business Logic: Access and modify messages in Exchange transport. Language Support: .NET Direct Property Access: Can access and change the content of messages in transport. Product Versions: Exchange 2007+ Summary: As...
  • Blog Post: About: Mailbox event and Notification APIs

    One with developing code for messaging development is to have code run when a specific event happens. Each mailbox API has its own ways of handling calls. Below is an overview of APIs which support events on the mailbox. Exchange Web Services (EWS): Exchange Web Service notifications are widely...
  • Blog Post: 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...
  • Blog Post: About: Exchange Store Sinks

    API Interface: COM interface implementation hosted in COM+. Business Logic: Store sink interfaces do not add or enhance business logic, see ExOLEDB or CDO for Exchange (CDOEX). Language Support: All COM compatible languages including .NET. Direct Property Access: Item access performed by ExOLEDB...
  • Blog Post: About: SMTP Event Sinks

    API Interface: COM interfaces. Business Logic: SMTP event sink interfaces which allow code to read and in cases modify a message during STMP transport Language Support: Event interfaces can be implemented using managed (.NET) code or C++ Direct Property Access: N/A Product Versions: Windows...
  • Blog Post: 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, Exchange Online. Summary Mail Apps for Outlook development allows you to write one application which will run in Outlook...
  • Blog Post: How to access the archive folder when user's mailbox is on-premise and the archive mailbox is in the cloud.

    If you have found that accessing a cloud archive folder is not working using the EWS Managed API when the user's mailbox is on-premise then you may need to add some code to your application. To get it to work you will either need to know the password for the archive mailbox or much better is to have...
  • Blog Post: EAS Inspector for Fiddler 1.4

    For the 1.4 released I've added the preliminary EAS 16.0 schema fields. Note that these are not for the final release of EAS 16. I'll update it further when EAS 16 reaches RTM. See the following for the preliminary EAS 16.0 specs: MS-ASWBXML covers the EAS Schema https://msdn.microsoft.com/en-us...
  • Blog Post: EASTester 1.7 Released

    For the 1.7 released I've added the preliminary EAS 16.0 schema fields. Note that these are not for the final release of EAS 16. I'll update it further when EAS 16 reaches RTM. See the following for the preliminary EAS 16.0 specs: MS-ASWBXML covers the EAS Schema https://msdn.microsoft.com/en-us/library...
  • Blog Post: Best Practices - EWS is not generating ATTENDEE section for iCal/MIME/VCALENDAR pulled from a meeting.

    This is expected behavior. Per MSDN: Programmatically reestablishing meeting organizer/attendee relationships directly on the appointments is not supported. Calendar POST items do not have attendees per RFC and that's what is being generated. What would go into an ATTENDEE section of iCal is a relational...
  • Blog Post: About: Exchange Server ActiveSync (EAS)

    API Type: Mailbox Assessor API Interface: APIs which can send a POST. Business Logic: Works with mailbox and public folder content including items, folders and special settings. Development Languages: N/A. Property Access: Yes Product Versions: Exchange 2003, 2007, 2010, 2013, Exchange Online. Summary...
  • Blog Post: About: Exchange APIs to backup and restore data

    Summary: There limited supported ways to backup and restore data with Exchange programmatically. Backup Supported APIs can backup the data and restore properly. Some developers try using APIs which were not meant for backup up and restoring data in order to gain certain functionality - such approaches...
  • Blog Post: Code running against Outlook is very slow when PST or OST is on a network folder or non-physical/non-VHD drive.

    There is no support for performance issues with Outlook where the PST or OST are on a network folder or non-physical/non-VHD drive. See below: Limits to using personal folders (.pst) files over LAN and WAN links https://support.microsoft.com/en-us/kb/297019 Note Customers are responsible for both...
  • Blog Post: About: Mailbox Accessing APIs

    These APIs are used to access folders and items inside mailbox and public folder stores. These are the APIs used to create mail client applications. They have varying levels of business logic available - not all APIs have objects for working with specialized item types like contacts, appointments, tasks...
  • Blog Post: 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...
  • Blog Post: About: SMTP Sending APIs

    Summary: Microsoft has several APIs which send email by SMTP. These 'SMTP Senders' are meant to send email to SMTP servers and do not have access to a mailboxes or public folders. Mail submitted by SMTP will not be saved into the Sent Items of the sender's mailbox. The beauty of these APIs is that...
  • Blog Post: Events from mailbox activity

    One with developing code for messaging development is to have code run when a specific event happens. Each mailbox API has its own ways of handling calls. Below is an overview of APIs and other mechanisms which support events on the mailbox. Exchange Web Services (EWS): Exchange Web Service notifications...
  • Blog Post: About: System.Net.Mail (SNM)

    API Type: SMTP Sender API Interface: .NET Framework Namespace Classes. Business Logic: Sending mail via SMTP. Language Support: .NET Languages only. Direct Property Access: N/A. Product Versions: .NET Framework 2.0 and later (as of .NET 3.5). Summary: SNM is a pure .NET namespace...
  • Blog Post: About: Exchange PowerShell Automation

    API Type: Exchange Administration API Interface: .NET Framework Class Libraries Business Logic: Managing mailboxes, storage groups, and databases. Language Support: Any .NET language. Direct Property Access: N/A Product Versions: Exchange 2007 and later. Summary: Exchange PowerShell...
  • Blog Post: About: Office 365 REST APIs for Exchange

    API Type: Mailbox Assessor API Interface: REST, JSON, OAuth v2 over HTTP Business Logic: Works with content in mailboxes such as Mail, Calendar, Contacts Development Languages: Anything which can send a post. So, you can write code for iOS, Droid, Windows forms, ASP.NET, JavaScript, PowerShell... Property...
  • Blog Post: About: Outlook Object Model (OOM)

    API Type: Mailbox Accessor API Interface: COM Library Business Logic: Richest Outlook item support (Mail, Tasks, Calendar, etc.). Language Support: All COM compatible languages including .NET. Direct Property Access: Only available in OOM for Outlook 2007 and later. Summary: Outlook...
  • Blog Post: About: WebDav

    API Interface: Mailbox Accessor API Interface: HTTP Protocol Extension Business Logic: Mail, Contacts and Simple Calendaring. Language Support: Any language that can submit XML formatted HTTP requests Direct Property Access: Yes. Product Versions: Exchange 2000, Exchange 2003 and Exchange 2007 Summary...
  • Blog Post: About: System.Web.Mail (SWM)

    API Type: SMTP Sender API Interface: .NET Framework Namespace Classes. Business Logic: Sending mail via SMTP. Language Support: .NET Languages only. Direct Property Access: N/A. Product Versions: All versions of .NET Framework (as of 3.5). Summary: The System.Web.Mail namespace was...
  • Blog Post: About: CDO for Windows 2000 (CDOSYS)

    API Type: SMTP Sender. API Interface: COM Library. Business Logic: Sending mail via SMTP Language Support: Works with both managed (.NET) and unmanaged code and scripting languages such as VBScript. Direct Property Access: N/A. Product Versions: Windows 2000 and later. Summary: CDOSYS has been...
Page 1 of 9 (205 items) 12345»