通过

What’s new in Azure Mobile Services - 2014-02-24

  • 项目

Here’s what has been added in Azure Mobile Services:

  • node.js runtime (version 0.1.6.2973)
    • Integration with notification hubs for push: your mobile service can now use the power of notification hubs to send push notifications to your clients. Check this post for more details.
  • .NET runtime (version 1.0.191) [preview]
    • A long awaited feature is now live: you can now create mobile services using .NET in the backend instead of node.js. Check out the getting started documents for more information (Windows Store / C#; Windows Store / JS; Windows Phone; iOS)
    • Notification hubs integration for push is also enabled for this runtime (it’s actually the only option, unless you want to talk to the authentication providers directly).

As usual, feel free to send us questions and comments in this blog or in our forums.

P.S.: Now that we have two different runtime types, the titles of these posts will not be based on the runtime version, but on the week where it was released instead.

Comments

  • Anonymous
    February 23, 2014
    Then I think you meant 2014-02-24. :D
  • Anonymous
    February 24, 2014
    Oops, thanks Robert! Fixed it.
  • Anonymous
    February 27, 2014
    Is there a way to migrate to .net backend on an existent mobile services?
  • Anonymous
    March 02, 2014
    I've tried the .NET backend but it seems like it's impossible to get the Access Token from OAuth2 Identity. I've tried the equivalent method getIdentities we have in node.js for a user object. This has a private accessToken property but it's null even when I'm authenticated.In Controller:((ServiceUser)this.RequestContext.Principal).GetIdentitiesAsync().Result
  • Anonymous
    April 01, 2014
    @Nicolai, there was a bug for retrieving the access token when using Google authentication, but it has been fixed in the latest release. Please let us know if you still encounter this problem@Francisco, no, there's no automatic way to migrate between a node.js and a .NET mobile service. The two frameworks are fundamentally different (see blogs.msdn.com/.../net-runtime-for-azure-mobile-services-first-impressions.aspx for a list) that such automatic migration, while possible in theory, may not yield the best results.