Browse by Tags

Tagged Content List
  • Blog Post: We’re Moving To The Microsoft Azure Blog

    We are continually looking for ways to make it easier for you to stay on top of the latest product releases, resources, tools and news around Azure Mobile Services and Microsoft Azure in general.  Today, we’re happy to announce another step in that direction with the consolidation of this team blog...
  • Blog Post: Offline support in the Azure Mobile Services iOS SDK

    We’ve just released a preview version of the Azure Mobile Services SDK for iOS with offline support. Like the offline support in the .NET SDK, we're releasing a preview version of the offline so that we can get feedback (from you!) to make sure that we release this feature in a way that will suit your...
  • Blog Post: Bring Your Own Database with the .NET Backend

    Azure Mobile Services helps provision a database for you when you create a new mobile service. But what if you want to connect to your own, existing SQL Azure database with the .NET backend? For example: You have an existing Mobile Service that uses the Node backend and has a lot of data in the...
  • Blog Post: Tables with Integer Keys and the .NET Backend

    A question I've seen asked a few times on our internal email lists "how to expose tables that have integer keys in the database through the .NET Backend?". The key is to use AutoMapper (see Mapping between Database Types and Client Types in the .NET Backend using AutoMapper an introduction). For example...
  • Blog Post: Fixing errors when publishing different projects to a .NET backend

    Quick post today. A few people in our team (and one in the forums) have hit an issue for which the current error logging doesn’t help too much, so write about this issue here. The problem is that when you try to publish a project to a mobile service where another project had been published before – even...
  • Blog Post: Logging with the .NET backend for Azure Mobile Services

    On the node.js version of mobile services, logging was done mostly via the node’s console object. In any of the server scripts you could call console.[log|warn|error] and when that script was executed you could go to the “logs” tab in the portal to see them. In the .NET backend you still have the same...
  • Blog Post: Creating MongoDB-backed tables in Azure Mobile Services with .NET backend

    One of the advantages of the .NET backend for Azure Mobile Services is that it has out-of-the-box support for multiple data storages, not only SQL Azure. In the node.js runtime you could bypass the SQL operations and use some other storage option (as in this post by Chris Risner for Azure Table Storage...
  • Blog Post: Creating an Azure Mobile Services .NET backend from scratch

    When learning a new feature I often like to understand the minimum pieces necessary to get it running. In the case of the .NET backend of azure mobile services, that would mean the smallest number steps required to go from an empty project to a running mobile service – no additional tooling required...
Page 1 of 1 (8 items)