Skip to content
This repository
branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 docs
Octocat-spinner-32 library
Octocat-spinner-32 samples
Octocat-spinner-32 .gitignore
Octocat-spinner-32 LICENSE
Octocat-spinner-32 README.md
README.md

Deprecated

This Toolkit is now deprecated and is superseded by Windows Azure Mobile Services.

The Windows Azure Toolkit for Android provided developers with the first iteration of support for building backend services for Android apps using Windows Azure. The main areas of feedback we received from mobile developers was that they wanted a turn-key set of services for common functionality such as notifications, auth, and data. Windows Azure Mobile Services directly reflects this feedback by enabling developers to simpily provision, configure, and consume scalable backend services. All future improvements will be channeled into Windows Azure Mobile Services rather than this toolkit.

To get started with Mobile Services, sign up for a Windows Azure accound and receive 10 free Mobile Services.


Windows Azure Toolkit for Android - v1.0.0

The Windows Azure Toolkit for Android is a toolkit for developers to make it easy to work with Windows Azure from native Android applications. The toolkit can be used for native Android applications developed using Eclipse and the Android SDK.

The toolkit works in two ways – the toolkit can be used to access Windows Azure storage directly, or alternatively, can go through a proxy server. The proxy server code is the same code as used in the Windows Azure Toolkit for Windows Phone and negates the need for the developer to store the Windows Azure storage credentials locally on the device. If you are planning to test using the proxy server, you’ll need to download and deploy the services found in the cloudreadypackages here on GitHub.

The Windows Azure Toolkit for Android is made available as an open source product under the Apache License, Version 2.0.

Contact

For additional questions or feedback, please contact the team.

Something went wrong with that request. Please try again.