Browse by Tags

Tagged Content List
  • Blog Post: Fresh Updates to Azure Mobile Services .NET

    Today we are rolling out a new set of updates to Azure Mobile Services .NET including: Better SQL Azure database initializers, Using local config settings, and Detecting when the service is unhealthy. Azure Mobile Services provide an easy way for building cloud connected mobile applications across any...
  • Blog Post: Real-time with ASP.NET SignalR and Azure Mobile .NET Backend

    We just released an update for Azure Mobile Services .NET backend which enables you to use ASP.NET SignalR for real-time, bi-directional communications with your mobile applications. SignalR will use WebSockets under the covers when it's available, and fallback to other “techniques” (i.e. HTTP hacks...
  • 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: Retrieving data from 1:n relationship using .NET backend Azure Mobile Services

    The .NET backend for Azure Mobile Services makes it easy to expose related tables via Entity Framework. However, related entities are not returned by default - for example, if you retrieve the list of orders from your orderController, it will not return the order items unless you explicitly ask for it...
  • 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: Mapping between Database Types and Client Types in the .NET Backend using AutoMapper

    Most of the samples showing how to use the .NET Backend have a single type that represents both the data stored in the database and the data that is exposed to the service callers. However, sometimes you cannot expose your database data as-is, or you want to provide and accept extra data to callers that...
  • 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: Autofac and Azure Mobile Services .NET Backend

    When creating an Azure Mobile Service .NET backend we automatically set up Autofac to deal with all things dependency injection. If you are new to Azure Mobile Services then here are tutorials and more . If you are not familiar with Autofac then they have a great wiki with lots of information . If you...
  • 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 (11 items)