This project is being archived and replaced with the Build Xamarin apps with the Microsoft Graph SDK training. As part of the archival process, we're closing all open issues and pull requests.
You can continue to use this sample "as-is", but it won't be maintained moving forward. We apologize for any inconvenience.
- Prerequisites
- Register and configure the app
- Build and debug
- Run the sample
- How the sample affects your account data
- Contributing
- Additional resources
This sample project demonstrates how to use the Microsoft Graph as the only back-end component for a complete property management solution. The samples covers features such as property details, conversations, files and tasks in a Xamarin Native app.
The purpose of this sample is to demonstrate the ability to create platform user interfaces and experiences (by implementing native views), while sharing common code across platforms and supercharging the solution with the Microsoft Graph. It heavily leverages Office 365 groups in order to organize data into properties.
Note The sample targets the beta branch of the Microsoft Graph, which the Microsoft Graph .NET Client SDK does not implement. Instead, network calls are being made with the built in HTTP stack towards the Microsoft Graph to consume its resources.
The samples uses the Microsoft Authentication Library (MSAL) for authentication and the MvvmCross library to bring the MVVM pattern across platforms with Xamarin.
| Project | Author(s) |
|---|---|
| XamarinNativePropertyManager | Simon Jäger (Microsoft) |
| Version | Date | Comments |
|---|---|---|
| 1.0 | August 4th 2016 | Initial release |
| 1.1 | April 4th 2018 | Updated to use MSAL library for auth |
This sample requires the following:
- Visual Studio 2017 with the Xamarin workload installed
- Windows 10 (development mode enabled)
- An Office 365 account - If you are building for Office 365 and you're missing an Office 365 tenant - get yourself a developer account at: https://developer.microsoft.com/en-us/office/dev-program.
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
You can use the Visual Studio Emulator for Android if you want to run the Android project.
-
Navigate to the the Azure portal - App registrations to register your app. Login using a Work or School Account.
-
Select New registration. On the Register an application page, set the values as follows.
- Set Name to Xamarin Native PropertyManager.
- Set Supported account types to Accounts in any organizational directory.
- Leave Redirect URI empty.
- Choose Register.
-
On the Xamarin Native PropertyManager page, copy and save the values for the Application (client) ID and the Directory (tenant) ID. You will need them in step 7.
-
Select Certificates & secrets under Manage. Select the New client secret button. Enter a value in Description, select any option for Expires and choose Add.
-
Copy the client secret value before leaving the page. You will need it in the next step.
-
Open the sample solution in Visual Studio and then open the Constants.cs file. Change the Tenant string to the Directory (tenant) ID value you copied earlier. Similarly, change the ClientIdForAppAuthn string to the Application (client) ID value and change the ClientSecret string to the client secret value.
-
Return to the Azure Active Directory management center. Select API permissions and then select Add a permission. On the panel that appears, choose Microsoft Graph and then choose Application permissions.
-
Use the Select permissions search box to search for the following permissions: User.Read, Group.ReadWrite.All, Sites.Read.All, Files.ReadWrite.All, Tasks.ReadWrite, Directory.Read.All. Select the check box for each permission as it appears (note that the permissions will not remain visible in the list as you select each one). Select the Add permissions button at the bottom of the panel.
-
Choose the Grant admin consent for [tenant name] button. Select Yes for the confirmation that appears.
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.
-
Open the Constants.cs file inside the XamarinNativePropertyManager (Portable) project of the solution.
-
After you've loaded the solution in Visual Studio, configure the sample to use your Azure AD tenant by replacing the [TENANT_ID_OR_NAME] value in the Authority property in the Constants.cs file.
-
Configure the sample to use your Azure AD application Client Id by replacing the [CLIENT_ID] value in the ClientId property in the Constants.cs file.
-
Open the XamarinNativePropertyManager.Droid/Properties/AndroidManifest.xml file. Replace the
[CLIENT_ID] value with your client ID.Note: If you're using Visual Studio for Mac, be sure to click the Source tab after opening AndroidManifest.xml.
-
Open the XamarinNativePropertyManager.iOS/Info.plist file. Select the Advanced tab and locate the URL Types section. Replace
[CLIENT_ID]with your client ID.
-
Select the project that you want to run. If you select the Universal Windows Platform project, you must run the sample on a Windows machine. If you want to run the iOS project, you'll need to either connect to a Mac that has the Xamarin tools installed on it, or you'll need to build and run the project in Visual Studio for Mac. The Android project can be built and run on either Windows or Mac as long as the Android emulator is installed.
-
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.
After launching the app, click the Sign in button to sign in to your organizational account. After you authenticate, the app displays all the properties in your organization. Create a new one by filling in the details and the app will provision a new Office 365 group for this property. At this point you will be able to post messages to the group conversations, add files and create tasks.
You will also be able to update the details of the property and create new ones. Explore the Office 365 groups in your browser to find all of the data used within the app. The property details are stored in an Excel workbook named Data.xlsx, located in the Property Managers group.
When this sample is started for the first time (in the Office 365 tenant) an Office 365 group named Property Managers is created. In this group, a Data.xlsx file is stored which hosts all of the details for the different properties.
For each property that is created within the app, a new Office 365 group is provisioned. In each group the files, conversations and tasks resources are used by the app. Tasks are the only thing that can be deleted (completed) from within the app. The app does not provide an ability to delete conversation posts or files.
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
- Simon Jäger's blog on #Office365Dev
Copyright (c) 2016 Microsoft. All rights reserved.