Skip to main content
WindowsAzure.MobileServices.Backend.Entity package icon

WindowsAzure.MobileServices.Backend.Entity

This package contains everything you need to expose structured storage using Entity Framework as part of your .NET mobile backend hosted in Microsoft Azure. For more information, check out http://azure.microsoft.com/mobile DEPRECATED: Azure Mobile Services is now deprecated in favor of Azure Mobile Apps. This library should not be used for new projects. To learn more, see: - https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-value-prop-migration-from-mobile-services/ - https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-net-upgrading-from-mobile-services/ - https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-client-and-server-versioning/

Total Downloads
111.4K
111,423
Published
Nov 23, 2015
Latest stable version

Install

.NET CLI
dotnet add package WindowsAzure.MobileServices.Backend.Entity --version 1.0.478
Package Manager Console
Install-Package WindowsAzure.MobileServices.Backend.Entity -Version 1.0.478
PackageReference
<PackageReference Include="WindowsAzure.MobileServices.Backend.Entity" Version="1.0.478" />

Frameworks

No framework metadata available.

Dependencies

[2.1.0, 2.1.0]
[3.5.2, 3.5.2]
[3.2.1, 3.2.1]
[6.1.1, 6.1.1]
[5.6.2, 5.6.2]
[5.6.2, 5.6.2]
[3.0.0, 3.0.0]
[6.0.4, 6.0.4]
Owin
Any
[1.0.0, 1.0.0]
[5.6.2, 5.6.2]

Adoption guide

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

NuGet marks this package as deprecated. Review the publisher's migration guidance before adopting it.

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

No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.

The published metadata declares 16 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.