DemoScript for Deck Developing Windows Phone apps using Windows Azure Mobile Services
Перейти к файлу
Cory Fowler aa55ee9684 updating .gitignore; fixes for automating packaging 2013-11-12 15:43:09 -08:00
Images first draft for demo script for WP deck 2013-02-05 17:04:53 -08:00
Source/Assets first draft for demo script for WP deck 2013-02-05 17:04:53 -08:00
.gitignore updating .gitignore; fixes for automating packaging 2013-11-12 15:43:09 -08:00
Demo.md Deleted unnecessary files and fixed line endings. 2013-07-04 13:18:53 -03:00
Demo.xml Update Demo.xml 2013-05-29 12:36:49 -03:00
LICENSE.md first draft for demo script for WP deck 2013-02-05 17:04:53 -08:00
README.md Update README.md 2013-02-07 15:00:37 -08:00

README.md

Getting Started with Windows Azure Mobile Services for Windows Phone#

Demo

Introduction

Demos are sets of step-by-step guides that are designed to help you learn how to use key Windows Azure services and features. Each demo provides instructions to guide you through the process of developing a complete application.

In this demo you will see how how you can leverage Visual Studio 2012 and Windows Azure Mobile Services to add structured storage, push notifications and integrated authentication to your Windows Store application.

You can find the FULL step-by-step DEMO.md script here

Note: You can download the latest build of the Windows Azure Training Kit which includes a tested version of this Demo from here: http://bit.ly/WindowsAzureTK.

Repository Structure

In the root folder of this repository you will find the script for this demo, Demo.md. Before beginning with the demo, make sure you have followed all the required steps indicated in the Setup and Configuration section of the document.

In the Source folder, you will find all the material necessary for this demo. The demo script will give you instructions on how to use this content. Typically, it will contain the following subfolders:

  • Setup: This folder contains the dependency files and the setup scripts necessary to initialize specific configurations of the demo. Its execution is required for the majority of the demos.

  • Code: This folder contains the source code required to perform the demo (usually there is a begin folder, which contains the starting code that you will complete by following the steps of the demo, and an end folder, which is the final result you should obtain once the demo is completed).

  • Assets: This folder contains common content that is necessary to complete the demo.

Get Started

In order to run the solutions provided by this demo you will first need to configure your environment and install any necessary prerequisites such as runtimes, components, or libraries. After cloning the Demo from the repository, follow the steps in the Setup and Configuration section of the Demo.md document.

Contributing to the Repository

If you find any issues or opportunities for improving this demo, fix them! Feel free to contribute to this project by forking this repository and make changes to the content. Once you've made your changes, share them back with the community by sending a pull request. Please see How to send pull requests for more information about contributing to Github projects.

Reporting Issues

If you find any issues with this demo that you can't fix, feel free to report them in the issues section of this repository.