azure-mobile-apps-net-server | The .NET server SDK for Azure Mobile Apps | Azure library

I'm a PM in App Center team at Microsoft. I'd like to share our continued commitment to Azure Mobile Apps as our team own it. We are doing user research right now to understand the evolving needs for these services and plan to build the next generation of Azure Mobile Apps as part of Visual Studio App Center.

While we're working on the roadmap, we are fully committed to supporting Azure Mobile Apps including support for the latest OS releases, bug fixes, and documentation updates.

This is a similar pattern to what we are doing with HockeyApp and Xamarin Test Cloud. App Center is the next generation for those services and as we roll their functionality into App Center, we are re-imagining key developer workflows and adding new features, as well as integrating them into an end-to-end CI/CD solution that helps developers ship better apps faster.

I'm a PM in App Center team at Microsoft. We are doing user research right now to understand the evolving needs for these services and plan to build the next generation of Azure Mobile Apps as part of Visual Studio App Center. While we're working on the roadmap, we are fully committed to supporting Azure Mobile Apps including support for the latest OS releases, bug fixes, and documentation updates.

To answer your question, Push Notification service in App Center is in "Preview" right now which means that there could be changes in the service while we are working to make it production ready. We don't recommend to not use this service for your "production apps". You can use Azure Mobile Apps as it stands currently but there won't any new features added to it. Based on your needs, you can make a decision on what service would be best suited for application.

Hope this helps.

Well I was able to solve it. I had configured my local server correctly since anniversary update at windows 10, when I updated to Creator Update it still worked fine, but recently here in Mexico i was offered to update to Fall Creators Update so I decided to update it.

after the update IIS Manager was uninstall from my OS, so I used WEB Plataform Installer from windows and reinstall it after it I could notice that my app user DefaultAppPool stopped even after I used at command prompt with administrator privileges so I create a new Application Pool with .NET CLR Version v4.0.30319 and Managed Pipeline mode: Integrated.

after that i used Microsoft SQL Server Management Studio I logged in to my local database and created a new user for my app, using as a user the App pool i just created and that did the trick.

After it I was able to made my backend work in debug mode in my local server and my client make its queries to my local server getting everything to as it was before.

Hopefully if somebody suffers the same experience as i did, this serves you as a solution for your local development enviroment.

.AddPushNotifications() is used to support the Azure Notification Hubs push registration endpoint via the Microsoft.Azure.Mobile.Server.Notifications package, you could check the NotificationInstallationsController.cs under the previous package. And at this point, you need to specific the Microsoft.Azure.NotificationHubs.ConnectionString app setting with the value for the connection string to your notification hub.

While the App Service Push is a feature provided by Azure Portal, and you need to go to your app service and click "Settings > Push", then choose your notification hub for your app, more details you could refer to here.

For your mobile client, you could leverage the extension method GetPush for IMobileServiceClient under MobileServiceClientExtensions.cs and the PushHttpClient.cs to send requests against push/installations for you. For more detailed code snippet, you could refer to here. Also, you could refer to adrian hall's book about using the .InvokeApiAsync() method.

You don't need to unregister and then register - a simple register will do it.

Check out chapter 5 of the book - http://aka.ms/zumobook - there is code within the chapter for each type of push registration that covers the Installation method (where you specify tags and templates together). You can then specify the SID explicitly by constructing a tag that is suitable for your needs.