Eric lippert - Amazon Web Services

Provide a Database Name, an Admin User and Password. Select
a Region that is closest to where you anticipate most traffic will
come from. Click on the ‘Complete’ button to finish the Wizard.
Azure will initiate the Service creation process.
selectively or via a broadcast.
Setting up the UI
The UI is very simple and won’t be winning any App Design
contests. All it has is three labels, three text boxes and a Send
Message Button.
11. Once the service is ready, click on it to navigate to the
Dashboard. In the dashboard, select the ‘PUSH’ tab to configure
push notifications. For Windows Application Credentials, provide
the Client Secret and Package SID we noted down earlier. Click on
‘Save’ at the bottom of the screen to save the changes
immediately.
Sending and Saving Data to Azure Mobile Service
Now that we have the UI setup, let’s work on saving data. To do
this, we have to switch back to the Mobile Service Dashboard.
Your App as well as Mobile Service is now set to work with WNS.
Building the Messaging Functionality
Now that we are all set, quick recap of what needs to be done
from here on
1. Setup our App to have three fields,
a. MyId – Current User’s Id
b. TweetText – Text of the FT or the FDM
c. ToID – An optional ID to send FDMs to.
1. Add the FakeTweetsMessage Table and click OK. The columns
will get created automatically once we post our Entity to it.
2. Save the above data in Azure Database. We’ll use Azure Mobile
Services for the same.
3. Write Code to retrieve Channel IDs
4. Utilize Channel IDs to send Push Notifications to others either
DNcmagazine www.dotnetcurry.com | 75