This project is read-only.

This Toolkit is now deprecated and is now

superseded by Windows Azure Mobile Services

During the early previews of Windows 8, the Windows Azure Toolkit for Windows 8 provided developers with the first support for building backend services for Windows Store 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 simply provision, configure, and consume scalable backend services. The downloads for this toolkit will be removed on the week of Feb 1st 2013.  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 account and receive 10 free Mobile Services.

Margie’s Travel

Running the Margie’s Travel Sample

Margie’s Travel is a sample travel application that demonstrates how you can track and manage your trips across multiple Windows 8 machines using a combination of technologies in Windows Azure and Windows 8. The application is a Metro styled app built on HTML5, CSS, and JavaScript.

The application does not require setting up. To run this sample, you must run both the client and the server application projects.

Note: This sample uses federated authentication to validate the credentials of the application’s users. Once a user has been authenticated, the information retrieved from the claims issuer is stored in a cookie to avoid repeating the logon process. In its present form, the sample sends this cookie in unencrypted form.

It is recommended that the cookie be encrypted for production applications. Please consider this if you plan to deploy the Margie's Travel sample to Windows Azure. For more information, refer to the ACS Security Guidelines (

  1. Open Visual Studio 2010 as an administrator.

    Note: At the time of writing, only Visual Studio 2010 supports Windows Azure cloud projects so you currently need to use this edition to launch the server application. This will change in a future release of the Windows Azure tools when support for Visual Studio 11 is enabled.

  2. Open the MargiesTravel.sln solution located in the Samples\MargiesTravel folder.
  3. Make sure that the start-up project of the solution is the cloud project. To set the start-up project, right-click the MargiesTravel.Cloud project in Solution Explorer and select Set as StartUp Project.
  4. Press F5 to launch the application in the compute emulator and open a browser window that shows its start page.


  5. Click login to show the list of configured identity providers.


  6. Click the identity provider of your choice and then sign in using your credentials.


    Note: Windows Live ID does not return claim with the user name. If you use this identity provider to sign in, the text shown in the upper right shows a string with your name identifier.

  7. Now, open Visual Studio 11 and open the MargiesTravel.Client.sln solution located in the Samples\MargiesTravel folder.
  8. Press F5 to launch the Metro style client application. Notice that the UI of the client Metro application is the same as the UI in the server, with both screens constructed using HTML.
  9. In the client application, click login to show the list of configured identity providers.
  10. Click the identity provider of your choice and then sign in using your credentials.


  11. Click any of the trips listed to view information about it.


  12. The cloud application also includes some rudimentary capabilities that allow you to test sending notification messages to registered clients. To, test notifications, type in the address bar of the browser and press ENTER.
  13. The browser displays a page that lists all registered clients. Verify that the list includes the Margies.Travel.Client.App client. Click the button labeled “Upgrade for (…)” in the Margies.Travel.Client.App row to upgrade and send a notification to this client.


  14. After a brief pause, you should receive a toast message with information about the upgrade.


    Note: To send notifications messages, you require a valid authentication token. If a token expires, you will not be able to send notifications. If you have trouble with these feature, sign in again to refresh the token.

Last edited Jan 21, 2013 at 8:59 PM by nharris, version 6


No comments yet.