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…


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 capabilities,…


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 are not…


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), but it’s…

7

Azure Mobile Services Managed Client SDK 1.3 alpha2

We released an update to  v1.3 of Managed Client SDK. It has following changes: Bug fix for issue related to synchronization of multiple items with version property on a table  We replaced TableName property on the operation object with instance of remote table i.e. IMobileServiceTable You can get the update from nuget http://www.nuget.org/packages/WindowsAzure.MobileServices/1.3.0-alpha2. If you’re building…


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. Currently the…

6

Push Notifications Using Notification Hub and .NET Backend

When creating a Azure Mobile Service, a Notification Hub is automatically created as well enabling large scale push notifications to devices across any mobile platform (Android, iOS, Windows Store apps, and Windows Phone). For a background on Notification Hubs, see this overview as well as these tutorials and guides, and Scott Guthrie’s blog Broadcast push…


Deep dive on the offline support in the managed client SDK

Last week we announced a new feature in the Azure Mobile Service SDK (managed code only for now): support for offline handling of data. While before all table operations required an active internet connection, with this new support the application can store table operations in a local data store, and later when connected push the…

14

What’s new in the Azure Mobile Services client SDKs 1.1.5 (and 1.1.4)

Last week we released the version 1.1.5 of all platforms of our client SDKs. Since we did not have a blog post for the changes in 1.1.4, I’m including them here as well: Managed (C# / VB) Added support for Azure Notification Hubs integration (added on 1.1.4): a while back we released a better integration…