Google Ads is used on many websites (and web applications). Can I use Google Ads in .Net Forms application? Does anybody know an API for this?
Google Adsense is not allowed in any desktop applications.
From Adsense policy
"Google ads, search boxes or search results may not be:
- Integrated into a software application of any kind, including toolbars.
- Displayed in pop-ups or pop-unders.
- Placed in emails, email programs, or chat programs.
- Obscured by elements on a page.
- Placed on any non-content-based page. (Does not apply to AdSense for search or mobile AdSense for search.)
- Placed on pages published specifically for the purpose of showing ads.
- Placed on pages whose content or URL could confuse users into thinking it is associated with Google due to the misuse of logos, trademarks or other brand features.
- Placed on, within or alongside other Google products or services in a manner that violates the policies of that product or service"
www.google.com/adsense/policies
And still if you want to do it then use web browser control in your application and give it the url , this url should be the page which will contain google ads..
it is only for web application not in desktop application ,Try to catch add yourself for the application.
for more details Google Adsence
Related
My app fetchers selling digital goods and I don't want to use in-app purchases for this purpose instead I would like to
use pesapal integration with the help of a WebBrowser control. I have checked the store policies regarding this as well as the
WebBrowser control security best practices for Windows Phone 8 but now confused since I am not still sure if it is legal and will my app be
rejected if I integrate payment using a WebBrowser control. ? Any help is appriciated...
Based on your description, we know you want to sell digital goods in your app. According to the Windows Store Policies 10.8 Financial Transactions, we can know that you could need to use the Microsoft in-app purchase API to sell digital items or services that are consumed or used within your app.
You could need to use a secure third party purchase API for purchase of physical goods or services, real world gambling or charitable contributions.
Please note only the tester can pass/fail an app.
It is possible to use a Web controller to load payments, we did this for Ticketsasa.com Application and it was approved before we changed to the current one which uses a different approach. The requirement however is that you must inform the user prior to loading the Web controller that by clicking of a button (or the event that loads the web Controller) will lead them to be redirected to a webpage where they will pay.
I've just taken a Facebook app live (ie: it's a web app that lives at apps.facebook.com). The app is a simple form that allows you to vote for one of four options. When submitting the form for the vote we also capture the FB ID in order limit the user to 4 votes per day.
When testing this app in sandbox mode as well as live in any browsers, the app functions fine. It even has exception handling in the edge cases where the user is not FB authenticated etc.
The issue we have encountered is that when a user visits the app from within the iOS Facebook app, the link opens within the Facebook in app browser (based on the iOS UIWebView component I believe). When using it from this environment, when the form submits our server is producing a 500 error.
Now I know that the 500 error will be nothing to do with facebook since it is our application code, but my confusion arises from the fact that this only happens from the Facebook in app browser. We are currently going about trying to determine the nature of the 500 error (we do not have access the production environment and custom errors have been switched off).
My question is this: Does the Facebook in app browser behave differently or do things differently than the standard UIWebView or iOS Safari?
I am thinking of differences such as interfering with POST data, clearing FB login credentials etc.
In short yes the Facebook in app browser does behave differently than the standard UIWebView and iOS Safari web browser.
The Safari web browser and the UIWebView do use different user agents.
The Facebook embedded browser doesn't seem to post hidden form values. And I can't seem to find any debugging tools for the embedded browser used in the iOS app.
I might not be 100% true on this one but i think Facebook might still be using this browser for the iOS app. But support for this library has been discontinued and has not been updated in over 2 years.
https://github.com/facebook/three20/wiki/Using-integrated-web-browser-via-TTWebController
So in short the answer to your question is Yes, but finding a solution for this issue is another story.
I haven't found anything yet...
Good Luck!
I am trying to embed Facebook comment box in a windows 8 store app. Is it possible to directly integrate the comment box or are there any other alternative solutions?
What I am trying now >>>> create a web page and add the Facebook comment box to webpage. Then access the webpage that I created through a Webview control. But when I try to login to Facebook using the comment box's link, it will not open the login dialogue inside the webview but it opens the browser where my windows 8 Store app pulled to the background.
I would recommend that you use the Facebook API, as recommended by another SO user answering a similar question
There is a Facebook API for Windows 8
You can find an example on Github here
I haven't tried this API, but did a WPF app using a similar API and it's usually straight forward.
If you would like to, and I know you didn't ask about that - this is just a tip, there is a web authentication broker in the WinRT API's to enable single sign on (SSO) connections to OAuth providers like Facebook etc.
You can find a sample here
Hope this helps, best of luck.
I know I have seen apps that log me in using Facebook but never present me with an authorization screen. I can not, for the life of me, figure out how to do this with Windows Phone 7. The best I have been able to get is using the Facebook for C# SDK to get the authorization screen in a WebView. This looks hideous and the page does not even appear to be mobile ready.
I have searched high and low for an answer and have found nothing. Wondering if anyone can point me in the right direction to getting this to work?
Yes, I also saw this kind of apps (e.g. Spotify prompts you to enter your Facebook account credentials rather than using the normal authorization flow). My best guess is that they either some kind of premium partners and have access to some private APIs or they use custom authorization flows (e.g. when you authorize an app on a website, the system saves authorization key in the database. The same app id/secret is then used in Windows Phone app and all you need to do is to type in your email/username in order for the system to locate authorization key that was saved earlier).
I also don't like the approach of displaying Facebook login/auth using WebBrowser control (mostly because of UI inconsistency) but I'd say that this is still the way to go in most cases (because this is the official and recommended way of authorizing the app and all other approaches seem hacky for me and also have their disadvantages).
You will want to be using the "server-side authentication" approach. The following document describes how it works: Server-side authentication (read also OAuth Dialog documentation for how to configure the authentication dialog). You can change the way the UI looks by passing a display parameter (either to touch or wap).
Please note that display=touch is currently broken in Windows Phone - Facebook always falls back to wap which is deprecated and will be removed as per July 2012 update (corresponding case: Facebook API can't be used with Windows Phone apps). It's also among known issues on Facebook C# SDK project page: Facebook C# SDK - Known issues.
Hope this clarifies things a bit.
Ultimately I want to create a desktop app that allows users to update their own status, view status' of their friends, update pics etc. - basically a lot of the functionality the facebook website provides. Through looking through some tutorials and sample projects it seems that an app must be created for the facebook account. Now is this the facebook account of the developer (i.e. mine) - which will provide an API key that will allow any other user to log in?? Does every desktop project need to authenticate the user through a facebook dialog window to take the users' credentials?? Where does OAuth fit into this?? If anyone can shed any light as to the structure of the facebook api and the ways in which I can grant this functionality from say a WPF C# app for example I would really appreciate it.
EDIT: Before complaints of a potentially huge question or too 'vague', my question is specific to the integration/use of the facebook API in desktop applications - not how to then retrieve status feeds etc. I'll work that out myself.
Per Facebook documentation, all desktop apps will need to implement some form of web browser integration, whether embedded within the desktop app or controlled.
See: http://developers.facebook.com/docs/authentication/
Desktop Apps
Our OAuth 2.0 implementation does not include explicit desktop app
support. However, if your desktop app can embed a web browser (most
desktop frameworks such as .NET, AIR and Cocoa support embedding
browsers), you can use the client-side flow with one modification: a
specific redirect_uri. Rather than requiring desktop apps to host a
web server and populate the Site URL in the Developer App, we provide
a specific URL you can use with desktop apps:
https://www.facebook.com/connect/login_success.html.
Don't worry it took me two solid days of trial and error and re-re-reading of the documentation on authentication to finally "get" it.