• Prerequisites
• Register and configure the app
• Build and debug
• Run the sample
• How the sample affects your account data
• Add a snippet
• Questions and comments
• Contributing
• Additional resources

This sample project provides a repository of code snippets that use the Microsoft Graph to perform common tasks, such as sending email, managing groups, and other activities from within a Xamarin.Forms app. It uses the Microsoft Graph .NET Client SDK to work with data returned by Microsoft Graph.

The sample uses the Microsoft Authentication Library (MSAL) for authentication. The MSAL SDK provides features for working with the Azure AD v2.0 endpoint, which enables developers to write a single code flow that handles authentication for both users' work or school (Azure Active Directory) or personal (Microsoft) accounts, including Office 365, Outlook.com, and OneDrive accounts.

This library is suitable for use in a production environment. We provide the same production level support for this library as we do our current production libraries. During the preview we may make changes to the API, internal cache format, and other mechanisms of this library, which you will be required to take along with bug fixes or feature improvements. This may impact your application. For instance, a change to the cache format may impact your users, such as requiring them to sign in again. An API change may require you to update your code. When we provide the General Availability release we will require you to update to the General Availability version within six months, as applications written using a preview version of library may no longer work.

The app displays UI representing common user tasks, or 'stories'. Each story is comprised of one or more code snippets. The stories are grouped by the account type and permission level. The user can log into their account and run the selected stories. Each story turns green if it succeeds, and red if it fails. Additional information is sent to the Output window.

This sample requires the following:

• Visual Studio 2015
• Xamarin for Visual Studio
• Windows 10 (development mode enabled)
• Either a Microsoft or Office 365 for business account

If you want to run the iOS project in this sample, you'll need the following:

• The latest iOS SDK
• The latest version of Xcode
• Mac OS X Yosemite(10.10) & above
• Xamarin.iOS
• A Xamarin Mac agent connected to Visual Studio

You can use the Visual Studio Emulator for Android if you want to run the Android project.

1. Sign into the App Registration Portal using either your personal or work or school account.

2. Select Add an app.

3. Enter a name for the app, and select Create application.

   The registration page displays, listing the properties of your app.

4. Under Platforms, select Add platform.

5. Select Mobile application.

6. Copy the Client Id (App Id) value to the clipboard. You'll need to enter these values into the sample app.

   The app id is a unique identifier for your app.

7. Select Save.

Note: If you see any errors while installing packages during step 2, make sure the local path where you placed the solution is not too long/deep. Moving the solution closer to the root of your drive resolves this issue.

1. Open the App.cs file inside the Graph_Xamarin_CS_Snippets (Portable) project of the solution.

   

2. After you've loaded the solution in Visual Studio, configure the sample to use the client id that you registered by making this the value of the ClientId variable in the App.cs file.

   

3. If you are planning on signing into the sample with a work or school account that does not have admin permissions, you'll need to comment out code that requests scopes that require admin permissions. If you don't comment out these lines, you won't be able to sign in with your work or school account (if you sign in with a personal account, these scope requests are ignored.)

   In the GetTokenForUserAsync() method of the AuthenticationHelper.cs file, comment out the following scope requests:

   	"https://graph.microsoft.com/Directory.AccessAsUser.All",
       "https://graph.microsoft.com/User.ReadWrite.All",
       "https://graph.microsoft.com/Group.ReadWrite.All",
   

4. Select the project that you want to run. If you select the Universal Windows Platform option, you can run the sample on the local machine. If you want to run the iOS project, you'll need to connect to a Mac that has the Xamarin tools installed on it. (You can also open this solution in Xamarin Studio on a Mac and run the sample directly from there.) You can use the Visual Studio Emulator for Android if you want to run the Android project.

   

5. Press F5 to build and debug. Run the solution and sign in with either your personal or work or school account.

   Note You might have to open the Build Configuration Manager to make sure that the Build and Deploy steps are selected for the UWP project.

When launched, the app displays a list representing common user tasks, or 'stories'. Each story is comprised of one or more code snippets. The stories are grouped by the account type and permission level:

• Tasks that are applicable to both work or school and personal accounts, such as getting and sending email, creating files, etc.
• Tasks that are only applicable to work or school accounts, such as getting a user's manager or account photo.
• Tasks that are only applicable to a work or school account with administrative permissions, such as getting group members or creating new user accounts.

Select the stories you want to execute, and choose the 'run selected' button. You'll be prompted to log in with your work or school or personal account. Be aware that if you log in with an account that doesn't have applicable permissions for the stories you've selected (for example, if you select stories that are applicable only to a work or school account, and then log in with a personal account), those stories will fail.

Each story turns green if it succeeds, and red if it fails. Additional information is sent to the Output window.

##How the sample affects your account data

This sample runs commands that create, read, update, or delete data. It will not edit or delete your actual account data. However, it may create and leave data artifacts in your account as part of its operation: when running commands that create, update or delete, the sample creates fake entities, such as new users or groups, so as not to affect your actual account data.

The sample may leave behind such fake entities in your account, if you choose stories that create or update entities. For example, choosing the run the 'update group' story creates a new group, then updates it. In this case, the new group remains in your account after the sample has run.

This project includes two snippets files:

• Groups\GroupSnippets.cs
• Users\UserSnippets.cs.

If you have a snippet of your own that you would like to run in this project, just follow these three steps:

1. Add your snippet to the snippets file. Be sure to include a try/catch block.

    public static async Task<string> GetMeAsync()
    {
        string currentUserName = null;
   
        try
        {
            var graphClient = AuthenticationHelper.GetAuthenticatedClientAsync();
   
            var currentUserObject = await graphClient.Me.Request().GetAsync();
            currentUserName = currentUserObject.DisplayName;
   
            if ( currentUserName != null)
            {
                Debug.WriteLine("Got user: " + currentUserName);
            }
   
        }
   

2. Create a story that uses your snippet and add it to the associated stories file. For example, the TryGetMeAsync() story uses the GetMeAsync() snippet inside the Users\UserStories.cs file:

    public static async Task<bool> TryGetMeAsync()
    {
        var currentUser = await UserSnippets.GetMeAsync();
   
        return currentUser != null;
    }        
   

Sometimes your story will need to run snippets in addition to the one that you're implementing. For example, if you want to update an event, you first need to use the CreateEventAsync() method to create an event. Then you can update it. Always be sure to use snippets that already exist in the snippets file. If the operation you need doesn't exist, you'll have to create it and then include it in your story. It's a best practice to delete any entities that you create in a story, especially if you're working on anything other than a test or developer account.

3. Add your story to the story list in MainPage.xaml.cs (inside the CreateStoryList() method):

   snippetList.Children.Add(new CheckBox { StoryName = "Get Me", GroupName = "Users", AccountType = "All", RunStoryAsync = UserStories.TryGetMeAsync });

Now you can test your snippet. When you run the app, your story will appear as a new item. Select the check box for your snippet, and then run it. Use this as an opportunity to debug your snippet.

We'd love to get your feedback about the Microsoft Graph Snippets Sample for Xamarin.Forms project. You can send your questions and suggestions to us in the Issues section of this repository.

Your feedback is important to us. Connect with us on Stack Overflow. Tag your questions with [MicrosoftGraph].

If you'd like to contribute to this sample, see CONTRIBUTING.MD.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

• Other Microsoft Graph Connect samples
• Microsoft Graph overview
• Office developer code samples
• Office dev center

Copyright (c) 2017 Microsoft. All rights reserved.