{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Explosion°爆炸 的问题《Azure Mobile Services or ASP.NET MVC 4 Web API》','https://www.manongdao.com/q-1048645.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I've built an ASP.NET MVC 4 app with standard database query tasks and user authentication. Now I want to upload it to Windows Azure and build Windows 8 and Windows Phone client applications. Is it better to use Azure Mobile Services or ASP.NET MVC Web API for these tasks? I have used the Simple Membership Provider for user security, so I'm not sure how can I use it with Mobile Services. Any advices?
相关问题
- running headless chrome in an microsoft azure web
- Docker task in Azure devops won't accept "$(pw
- Register MicroServices in Azure Active Directory (
- PromptDialog Choice with List object Bot Framework
- Dotnet Core API - Get the URL of a controller meth
相关文章
- MVC CDN fallback for Style Bundle
- Add to htmlAttributes for custom ActionLink helper
- SQL Azure Reset autoincrement
- POSTing data to WebApi after update to 5.1.0 fails
- Can you use generic methods in a controller?
- How to cast Azure DocumentDB Document class to my
- Remove a route with IOperationFilter in SwashBuckl
- Disable action method from being called from the a
I don't think you can use anything aside from Live Connect/FB/Google/etc when dealing with ZUMO directly.
I suppose you could create your own web api or other web-based login that uses simple membership to validate user credentials. The server would subsequently make a login request to the live connect service (for any validated user) and return the authenticationToken along with the user object back to your app.