Multiple Windows 8 apps, can they share the same Azure Mobile Services backend? This was the question I was looking to answer this week. I did the prerequisite search of the interwebs and found that this question has been floating around for a while now. What I didn’t find was a definitive answer. Let’s start off by solving that problem.
The World Acording to Marc
I’ve been publicly building an application called RMV Awesome for the last several months on this blog. Since the initial release of the Windows 8.1 app we’ve migrated code to a Portable Class Library, ported to Windows Phone 8, added monetization and integrated Azure Mobile Services. Next we’ll tackle geo-location.
I’ve been trying off and on for some time now to add my Outlook.com account to Outlook 2013. I’ve used this setup for years but recently it stopped working. Every time I tried to add it Outlook would return an error. In one of those face-palm moments I realized what changed.
Part of a series covering Windows Client development. In this article we’ll integrate Azure Mobile Services into the awesome RMV Awesome app.
Part of a series covering Windows Client development, we continue to work on RMV Awesome – an ironically named Modern UI application for keeping tabs on the Massachusetts Registry of Motor Vehicles. In this article we’ll start monetizing our app use the Microsoft Advertising SDK.
Monetization is one of the most important and confounding choices a developer has to make. I spend most of my day working with developers and organizations building commercial software. App monetization is one of those topics that seems to come up fairly regularly.
Back in October I wrote about a little app I built for Windows 8.1 called Image Importer. It is a rather simple app designed to replace two features previously available in Windows Essentials Live Gallery – the ability to import files into folders by Date Taken and remove files from the source media when completed. Since then I’ve made a few updates and learned a few lessons.