Skip to main content

MEC from a developers perspective

The Microsoft Exchange Conference or (MEC as it is affectionately know) is being held in Orlando next month for the first time in 10 years. www.mecisback.com  . 10 years is a long time and in Technology even longer for example since the last MEC was held we have had

  • Blackberry's (started to appear around the last time MEC was held and starting to disappear now)
  • First IPhone June 2007 , ITunes and pretty much the whole Apps concept
  • First Windows Smart Phone (Pocket PC 2002)
  • Social Networking
  • FaceBook Feb. 4, 2004
  • Twitter November 4, 2008

 The term wave is used in the IT industry to convey the way in which different technologies wash through the rest of our lives and affect the way in which we work and relate to the world in general. In the later part of 2012 we are on the crest of another wave with all the following on the way or released already.
  • Windows 2012
  • Exchange 2012
  • Surface
  • Windows 8
  • IPhone 5 and Android Tablets and phones

 The great thing about technical conferences is that there are so many to choose from these days but MEC is special, because its no only just focused entirety on Exchange but because many of the sessions will be given are by the people responsible for producing and delivering the product. New products offer new work and opportunities for developers and entrepreneurs a like. MEC will really be the first and best opportunity to learn in-depth the changes and new opportunities the next version of the Exchange will give, as well as maybe learning a few things you don't know about current versions and making those important connections with your peers in the community and industry.

While like most conferences MEC is more aimed at the IT Pro rather then specifically for developers here are a few sessions any self respecting Exchange Dev shouldn't miss.

Apps for Outlook and OWA [E15.307]
 
Labels:

Popular posts from this blog

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Gr...
Read more

Exporting and Uploading Mailbox Items using Exchange Web Services using the new ExportItems and UploadItems operations in Exchange 2010 SP1

Two new EWS Operations ExportItems and UploadItems where introduced in Exchange 2010 SP1 that allowed you to do a number of useful things that where previously not possible using Exchange Web Services. Any object that Exchange stores is basically a collection of properties for example a message object is a collection of Message properties, Recipient properties and Attachment properties with a few meta properties that describe the underlying storage thrown in. Normally when using EWS you can access these properties in a number of a ways eg one example is using the strongly type objects such as emailmessage that presents the underlying properties in an intuitive way that's easy to use. Another way is using Extended Properties to access the underlying properties directly. However previously in EWS there was no method to access every property of a message hence there is no way to export or import an item and maintain full fidelity of every property on that item (you could export the...
Read more

Sending a Message in Exchange Online via REST from an Arduino MKR1000

This is part 2 of my MKR1000 article, in this previous post  I looked at sending a Message via EWS using Basic Authentication.  In this Post I'll look at using the new Outlook REST API  which requires using OAuth authentication to get an Access Token. The prerequisites for this sketch are the same as in the other post with the addition of the ArduinoJson library  https://github.com/bblanchon/ArduinoJson  which is used to parse the Authentication Results to extract the Access Token. Also the SSL certificates for the login.windows.net  and outlook.office365.com need to be uploaded to the devices using the wifi101 Firmware updater. To use Token Authentication you need to register an Application in Azure https://msdn.microsoft.com/en-us/office/office365/howto/add-common-consent-manually  with the Mail.Send permission. The application should be a Native Client app that use the Out of Band Callback urn:ietf:wg:oauth:2.0:oob. You ...
Read more
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.