azure-mobile-services

问题 I created a fresh Azure Mobile Services project and published to a newly created service on Azure. I then published the project to Azure and verified that I could post/get from it. Next, I enabled migration via the nuget manager console by following a guide i found online online and that I found on MSDN to set up data migration. I walked through the steps, adding my initial migration and re-publishing it to Azure. I did not make any changes to my models. The only thing I did after the first

问题 I am trying to save an Entity with an ID and an DateTimeOffset in a AzureMobileServicesClient SQLite database in a Xamarin Forms application. This work fine as long as the time stamp is non ambiguous. When we go from daylight saving to standard time there is a period a time where a time stamp can be ambiguous depending on the timezone. In 2016 in Denmark it is 2:00-3:00 AM October 30th. I save the Entities DateTimeOffset as UTC, but it saves it as a local timestamp. When I save an ambiguous

问题 I am playing with an Azure Mobile Apps backend (nodeJS), as discussed here. I have been using the default web setup configuration to develop my mobile app, but now I want to customise the cloud backend functionality, so I have created a local backend with the Azure-Mobile-Apps SDK. I logged in with my mobile app (using the authorization aspect of the Azure client SDK) and then captured the AuthToken, using a live managed backend setup. When I then come to try and authorise a request, I get

问题 I'm playing around with this block of code: try { mscvUser = imstUser .Where(User => User.Id == intId) .Take(1000) .ToCollectionView(); } catch(MobileServiceInvalidOperationException f){ MessageBox.Show(f.ToString()); } It works fine normally, but I've been deliberately disconnecting my Internet for testing purposes, and I keep hitting MobileServiceInvalidOperationException, but it won't catch it in that block; it throws it back to App.xaml.cs, breaks, and shuts down the app. 回答1: I think you

问题 I've been struggling for hours to try and upload data to an Azure database (mobile service). My datamodel on the Azure database: My model in Xamarin Forms (the class): public class Test { public string Id { get; set; } [JsonProperty("XAxis")] public int XAxis { get; set; } [JsonProperty("YAxis")] public int YAxis { get; set; } } Writing the data to Azure: var test = new Test { XAxis = 100, YAxis = 200 }; await client.GetTable<Test>().InsertAsync(test); However when I execute this I will get

问题 I've been struggling for hours to try and upload data to an Azure database (mobile service). My datamodel on the Azure database: My model in Xamarin Forms (the class): public class Test { public string Id { get; set; } [JsonProperty("XAxis")] public int XAxis { get; set; } [JsonProperty("YAxis")] public int YAxis { get; set; } } Writing the data to Azure: var test = new Test { XAxis = 100, YAxis = 200 }; await client.GetTable<Test>().InsertAsync(test); However when I execute this I will get

问题 In my iOS app I'm trying to add push notifications via Azure Mobile Services. I have followed this article: https://azure.microsoft.com/en-us/documentation/articles/mobile-services-javascript-backend-ios-get-started-push/ But my app still receive no push notifications! In the iOS dev center I registered App ID with Dev and Production push certificates. Added Dev certificate (.p12) to Sandbox in the Azure. I wrote POST function exports.post = function(request, response) { var text = 'You\'ve

问题 I need a 1:n relationship using the Azure App Service. I followed this tutorial for the entities. My client entities (same as tutorial, except I added a constructor): public abstract class Entity { // defines id, version, createdAt, updatedAt, deleted } public class Animal : Entity { public string Name { get; set; } } public class Zoo : Entity { public Zoo() { Animals = new List<Animal>(); } public string Name { get; set; } public List<Animal> Animals { get; set; } } My server entities (same

问题 I am working in Azure Mobile Service where I have made a custom api. For those it is possible to set permissions (like public, application, user and admin), which is very useful. But I need multi-level api (like for example /api/user/profile/{userId} ), and to be able to set some permission to the sub-level api. I have found it is possible to add other levels of api paths with the following code exports.register = function (api) { /* Get public user profile on some other user */ api.get('

问题 I am working in Azure Mobile Service where I have made a custom api. For those it is possible to set permissions (like public, application, user and admin), which is very useful. But I need multi-level api (like for example /api/user/profile/{userId} ), and to be able to set some permission to the sub-level api. I have found it is possible to add other levels of api paths with the following code exports.register = function (api) { /* Get public user profile on some other user */ api.get('