Updating the Tools
If you already have the tools installed, look out for an update notification in Visual Studio.
If you can’t wait to update, then you can go ahead, download and update the tools here!
Updating the Client Libraries
Along with updating the tools, you should also update the client libraries if you are already using the libraries in an existing project. Just go to NuGet Package Manager and look out for updates to the Office 365 API Client Libraries and update them all.
Since you are moving from Preview, it is always advised that you remove all the Office 365 API NuGet packages and then install them via Office 365 API Tools.
Few notable changes
- Azure Active Directory Graph library has undergone a name change. So, if you are already using the AAD Graph library, you may want to uninstall the previous version and install the latest version.
- There has been quite few namespace changes, so look out for them when building the project.
- ExchangeClient is now OutlookServicesClient
- There is a new client for the Office 365 Discovery Service called DiscoveryClient
- The tools no longer adds sample code files to your project, instead redirects to the documentation portal where you will have instructions on how to write code against Office 365 APIs.
- Note: This document will be updated from time to time to reflect new information/updates.
Changes to Authentication Library
This is probably the biggest change you will notice. The libraries no longer have specific implementation for authentication.
You can use Active Directory Authentication Library to write code to authenticate against Windows Azure Active Directory.
To get started, you can view the awesome samples ADAL team has already published to GitHub – Here are a few that might interest you:
- WebApp-WebAPI-MultiTenant-OpenIdConnect-DotNet (replace the WebAPI calls to Office 365 API)
- WebApp-WebAPI-OAuth2-UserIdentity-DotNet (replace the WebAPI calls to Office 365 API)
- Client Applications Samples
Office Developer GitHub will also be updated with samples. Here is the first one that I published
This sample shows how to build an MVC web application that uses Azure AD for sign-in using the OpenID Connect protocol, and then calls a Office 365 API under the signed-in user’s identity using tokens obtained via OAuth 2.0. This sample uses the OpenID Connect, ASP.Net OWIN middleware and ADAL .Net.
Updates to dev.office.com and MSDN
Make sure you visit these links for some useful content:
As usual, do leave your comments and feedback if any!
Go Office 365 APIs! 🙂