Skip to main content
Microsoft.Azure.Mobile.Client package icon

Microsoft.Azure.Mobile.Client

This library provides features for creating Windows and Xamarin mobile apps that connect to Azure Mobile Apps. Azure Mobile Apps allows you to develop an app with a scalable backed hosted in Azure App Service, with support for mobile authentication, offline sync, and push notifications. To learn more about Azure Mobile, go to http://azure.microsoft.com/mobile.

Total Downloads
2.3M
2,266,937
Published
Dec 12, 2018
Latest stable version

Install

.NET CLI
dotnet add package Microsoft.Azure.Mobile.Client --version 4.1.1
Package Manager Console
Install-Package Microsoft.Azure.Mobile.Client -Version 4.1.1
PackageReference
<PackageReference Include="Microsoft.Azure.Mobile.Client" Version="4.1.1" />

Frameworks

.NETFramework4.5 .NETPortable0.0-Profile259 .NETStandard1.4 MonoAndroid7.0 UAP10.0 Xamarin.iOS1.0

Dependencies

Newtonsoft.Json
.NETFramework4.5
[9.0.1, )
Microsoft.Net.Http
.NETPortable0.0-Profile259
[2.2.29, )
Newtonsoft.Json
.NETPortable0.0-Profile259
[9.0.1, )
PCLCrypto
.NETPortable0.0-Profile259
[2.0.147, )
NETStandard.Library
.NETStandard1.4
[1.6.1, )
Newtonsoft.Json
.NETStandard1.4
[9.0.1, )
[4.3.0, )
System.Linq.Queryable
.NETStandard1.4
[4.3.0, )
[4.3.0, )
Newtonsoft.Json
MonoAndroid7.0
[9.0.1, )
PCLCrypto
MonoAndroid7.0
[2.0.147, )
[23.3.0, )
[9.0.1, )
[4.0.1, )
Newtonsoft.Json
Xamarin.iOS1.0
[9.0.1, )
PCLCrypto
Xamarin.iOS1.0
[2.0.147, )

Adoption guide

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.

Compatibility metadata lists 6 target frameworks; confirm the exact target used by your application.

The published metadata declares 18 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.