Azure Mobile Service

 

image

Windows Azure Mobile Services:

  • A turnkey backend solutions to power your mobile apps on any platforms – iOS, Andrioid, Windows(Store/Phone) or Mac and tools like C#, Java, JavaScript, Xamarin, PhoneGap.
  • Accelerate your mobile app development. Incorporate structured storage in the cloud, user authentication(Facebook, Google, Microsoft, Twitter, Active Directory account)/authorization and push notifications to millions (Notification Hubs) in minutes. Add your custom backend logic in C# or Node.js
  • Introduction to Azure Mobile Service – Scott Guthrie

Below are some tutorials that walkthrough common authentication/authorization/push scenarios you can do with Windows Azure Mobile Services:

Azure WebJobs

 

  • Azure WebJobs 101 – Basic WebJobs with Jamie Espinosa
  • Azure WebJobs 102 – Scheduled WebJobs and the WebJobs Dashboard with Jamie Espinosa
  • Azure WebJobs 103 – Programming WebJobs in .NET with Pranav Rastogi
  • Azure WebJobs 104 – Hosting and testing WebJobs in .NET with the WebJobs SDK with Pranav Rastogi
  • Azure WebJobs 105 – Scaling out Web Jobs
  • Azure WebJobs 106 – The WebJobs Dashboard as a Site Extension
  • Azure WebJobs 107 – Cross Platform WebJobs
  • Azure WebJobs 108 – Notifications from WebJobs
  • Azure WebJobs 109 – Advanced WebJobs SDK Programming – a binding & trigger system which works with Azure Storage Blobs/Queues/Tables.
  •  

    Resources:

    Enabling Cross-Origin Requests in ASP.NET Web API

    Introduction

    This tutorial demonstrates CORS support in ASP.NET Web API. We’ll start by creating two ASP.NET projects – one called “WebService”, which hosts a Web API controller, and the other called “WebClient”, which calls WebService. Because the two applications are hosted at different domains, an AJAX request from WebClient to WebService is a cross-origin request.


    What is “Same Origin”?

    Two URLs have the same origin if they have identical schemes, hosts, and ports. (RFC 6454)

    These two URLs have the same origin:

    These URLs have different origins than the previous two:

    Internet Explorer does not consider the port when comparing origins.

    for more:  http://www.asp.net/web-api/overview/security/enabling-cross-origin-requests-in-web-api

    Also from Microsoft Web-API: http://www.asp.net/web-api/overview

    ASP.NET Web API 2–Token Authentication for SPA

    image

    Cylon.js with Raspberry Pi Resources

     

    image

     

    Tutorial:

    http://nemron.com/blog/cylon-js-on-raspberry-tutorial-making-the-led-blink/

    http://www.quietless.com/kitchen/controlling-24-leds-with-node-js-and-a-raspberry-pi/

    Connect to Android with ADB over WiFi

     

    image

    1. By default, the Android Debug Bridge (ADB) is configured to communicate with an Android device via USB. It is possible to to reconfigure it to use TCP/IP instead of USB. In order to do this, both the device and the computer must be on the same WiFi network. To setup your environment to debug over WiF issue these steps from the command line:
      • Determine the IP address of your Android device. One way to find out the IP address is to look under Settings > Wi-Fi, and then tap on the WiFi network that the device is connected to. This will bring up a settings screen showing information about the network connection.
    2. Connect your Android device to your computer via USB.
    3. Next restart ADB so that it using TCP on port 5555. From a command prompt, type the following command: adb tcpip 5555
    4. Disconnect the USB cable connecting your device to your computer
    5. Configure ADB so that it will connect to your Android device on the port that was specified in step 1 above:  e.g. adb connect 192.168.0.12:5555   Once this command finished the Android device is connected to the computer via WiFi.

    p.s.

    • When you are done debugging via WiFi, it is possible reset ADB back to USB mode with the following command: adb usb
    • To list the connected device, use the command: adb devices