i need a list of my application users.
i use facebook C# sdk
You should store your application users ids on your own...
Currently this isn't possible with API Facebook providing.
BTW,
Official Facebook C# SDK is deprecated so you may want to work with unofficial C# SDK hosted on Codeplex
Related
I have basic understanding of .net and chatbot.
I wanted to integrate Amazon lex in xamarin(ios, android)app. There seems to be no example or sample. I have created chatbot from AWS platform intent and slots.
Also I wanted to use database to get query return. Any sample to integrate AWS Lex with Xamarin app would be helpful.
As I understand from your question, you already have some implementation of chatbot made with AWS services, but you are having issue on integrating it to your xamarin application to be able to use it in IOS and Android devices.
For that purpose, there is AWS Mobile SDK which happens to support also xamarin.
From their link:
https://docs.aws.amazon.com/mobile/sdkforxamarin/developerguide/Welcome.html
I also did not find a Lex tutorial directly, but a very promising quote:
Supported AWS services currently include, but are not limited to [narrow list of services]
was on the same page. I looked around, found this text:
The AWS Mobile SDK for .NET and Xamarin also allows you to use most of the AWS services supported by the AWS SDK for .NET. The AWS services specific to mobile development are explained in this developer guide. For more information about the AWS SDK for .NET, see [a link]
clicked the link and ended here:
https://docs.aws.amazon.com/sdkfornet/v3/apidocs/Index.html
and under link AmazonLex -> AmazonLexClient there was something, you probably wanted to see:
Version Information
.NET Standard:
Supported in: 1.3
.NET Framework:
Supported in: 4.5, 4.0, 3.5
Portable Class Library:
Supported in: Windows Store Apps
Supported in: Windows Phone 8.1
Supported in: Xamarin Android
Supported in: Xamarin iOS (Unified)
Supported in: Xamarin.Forms
Those 3 last let me understand that whenever you setup Mobile SDK, you get access to AWS services in Xamarin, also Lex.
Steps to install on
https://docs.aws.amazon.com/mobile/sdkforxamarin/developerguide/setup.html
mainly contain steps on how to create xamarin app and get AWS account, most important is to install the AWS Mobile SDK for .NET and Xamarin and configure it. More detailed steps are under that link.
After that the process is to follow the instructions on:
https://aws.amazon.com/getting-started/projects/bots-just-got-better-net-toolkit-lex-lambda-cognito/module-one/
like pointed in comments. I suppose once you have access to any service via Mobile SDK, the wire up of Lex may go in similar steps and no special just xamarin tutorial is not needed anymore.
It seems you are looking for both architecture and sample code for implementing AWS Lex bot with .NET backend that can be integrated with iOS/Android Frontend.
You have multiple choices here to do it
Build both chat user interfaces in iOS and Android and integrate them AWS iOS & Android SDKs to utilize the AWS LEX bot.
Just implement a bot user interface in iOS and Android app and integrate it with a .NET backend that can utilize AWS .NET SDK to integrate with your LEX bot.
I would recommend the second approach as it will save you writing the LEX integration code twice both in Android and in iOS. In the second appraoch you will be able to write a single integration for AWS LEX in .NET and that can give a unified experience across the mobile devices(iOS/Android)
Now for the .NET based backend integration with AWS LEX bot.
If you are an experienced .NET developer and you know how will you host your code then only thing that you need is the .NET API reference for AWS LEX, which can be found here
https://docs.aws.amazon.com/sdkfornet/v3/apidocs/items/Lex/TLexClient.html
But if you are not sure how to write this integration code and also not sure how the deployment will look like then you can follow the below tutorial
Bots Just Got Better with .NET and the AWS Toolkit for Visual Studio
Also, find here the architecture form the above tutorial
there is no direct solution like Amazon Lex is supported by React-native. i confirmed with xamarin team as well as AWS service one of the member. direct integration not possible.
I've successfully implemented Facebook login with their Javascript SDK but was hoping that when used on mobile, the native Facebook application would launch. Will going through the manual flow here allow this behavior? This question seems to say otherwise but was vague.
I want to avoid using Android and iOS mobile SDKs because my situation is basically an OAuth within an OAuth and it would get messy. Any other approaches people think could work like redirect URIs or other OAuth magic would be really appreciated.
I implemented a php application that creates events in google calendar. But i need also to create resources, and i found the documentation for Google Apps Calendar Resource API
My first question is: where can I download the API files.
And second: i can use this in PHP? Because in the examples that they provide, they use only .NET and Python.
Thank you!
This API uses an older Google APIs technology stack called GData. There is a GData PHP client library built into the Zend framework, but it doesn't support OAuth2 and doesn't include support for this particular API. You're only option is to construct the OAuth2 tokens, XML body, and HTTP requests yourself using the documentation as a guide.
We know how to call Facebook Graph API v1.0 and are calling it in the iOS SDK (https://developers.facebook.com/docs/apps/upgrading) but new users are getting treated as though they're signing up with v2.0.
We know that once a user logs in via Graph API v2.0, there is no going back to v1.0 for that individual user (http://code-worrier.com/blog/changes-in-facebook-graph-api-2-dot-0/) but does anyone know if all new users to your app will automatically login through v2.0 and only previous users can login v1.0? We're using the Facebook iOS SDK v3.14.
Thanks so much.
New users signing up for your application since 4/30/2014 will return app-scoped id's. The version you use in the URL for the API request won't change that.
Here's what we found out: you can still log into / use the old version of the Facebook API (v1.0). The issue is the API version that gets called by your app depends on the Facebook iOS SDK version you are using in your app. So if you want to jump back to pre-v2.0 Facebook API, you need to be using an old version of the Facebook iOS SDK (3.13.1 and previous). They are all found here: https://developers.facebook.com/docs/ios/downloads
Keep in mind, Facebook is forcing developers to upgrade to v2.0 by April 30th of 2015. But, if you have a v2.0 headache now that you don't want to fix right away, this a decent band-aid solution. In our app, we upgraded the Facebook iOS SDK to get compliant with Apple's IDFA regulations, not knowing we were upgrading to v2.0 of the Facebook API. Since our app uses some features no longer available in v2.0, this was a huge issue.
Any users that may have signed up for your app while you were using v2.0 may need to delete app related info on Facebook so that they can log in fresh when you jump back to v1.0. This will allow you to get real Facebook user IDs and not app scoped user IDs.
The last small hurdle is that Apple is now rejecting many, if not all, apps that use the IDFA. All Facebook SDKs that use v1.0 use the IDFA (to my knowledge). The only way around it is to tell Apple that you are using it, but that it is attributed to a previously served advertisement (you do this on iTunes connect). See this article here: http://www.adexchanger.com/mobile/apple-throws-a-bone-to-app-marketers-blesses-idfa-for-attribution/
Again, this is not necessarily a 'proper' solution, but if you don't have the bandwidth / resources to fix your v2.0 issues right now, it can definitely help. Just make sure to get back to v2.0 before April 30, 2015.
Hi Guys
I am trying to create a web app to share docs with all editor features (just like google docs).
My main requirements for this app are as follows:
1. Should have all editor features (can be done using open office api, google docs api, Microsoft office web apps api)
2. Should be shared between multiple users and can be edited by multiple users and other sync features (can be done using google docs api, Microsoft office web apps)
3. Can save the document created and edited on my own/ custom server addr. (Which api can support this??? I know open office can support this)
Guys can you please suggest me one api which can be used to do all the above. Also please suggest if I am underestimating any API above regarding any functionality that i thing is not supported.
Thanks
King
What you are asking for is so complex it takes a Google to make a "in progress" version!
Can't you just use Google API? Its is free. Your only issue would be logging users via OAuth, 1 simple API