I am a new bee in the world of word press.Actually I am not a new to the wordpress or blogging sites like wordpress or blogger. I have my couple of blogs in blogger few time ago. But then I switched to the WordPress blogs and then ultimately had my own domain on which you are right now 🙂
Basically a main purspose of having a blog is to store information which can be useful to others and yourself and yeah as you will say making some money.
I am not the exception to this and for that I decided to have most successful advertising platform “Google AdSense”.
But as I said I am new bee in the world of wordpress, I am not familiar about how to get that setup in my own domain.
At that time google has come to my rescue and I found one plugin which does this job easily for me without any much hassle.
I know you all are curious to know the name of that plugin, so not making you wait longer I am reveling the name of that plugin.
So the name of that plug in issssss…. “Easy Google AdSense“
This is the coolest plugin I have came across to setup my adsense account in my word press site.
You can read their documentation to know How to install it and configure it with your Google Adsense account.
AS you all may know from the March 7,2019 google is going to shutdown the support for the Google+ API. This is going to be the progressive shutdown for the Google+ APIs.
So all the calls with the endpoint to the Google+ APIs will start to fail from the January 28,2019.
Google has already started the process of sending an email to their developers/users who are using the Google+ APIs. Even if you didn’t receive that email you must remove the use of that API or switch to some other api calls.
The most commonly used APIs that are being shut down include:
How to Export and then Import Info Path form in SharePoint Online?
While I was working with the project for one of my client. I got a requirement to make Info Path form work with the SharePoint Online. As you all may know that Info Path forms are bit tricky unless you have good understanding about that and how they work.
I was working on a provider hosted app. The main usage of this app is to convert the Info Path form in MVC based form and mimic the actual flow of data from Initialization of process to the Finalized/Completed the process.
To achieve this, I have a console application which will read the infopath as xml from sharepoint 2013 on premise site and convert them to the appropriate record for my new SharePoint Online module.
My Console application also export the attachments from the Info Path forms and save them in a document library with the main list column as lookup.
I know this whole conversation can make you confuse.
Let me know if you like to have a look in the console application and a code. I will be happy to assist you on that..
For more info: Visit my SharePoint site : https://trickycoder.sharepoint.com
During my sessions related to the share point I asked the students to define the difference between SharePoint Hosted App and Provider Hosted app. They provide some fundamental differences but no one is able to give proper answer.
So here I am providing a list of differences from the user/client perspective so that you can decide which app approach needs to be chosen for your project work.
No server side code, 100% client side code
Managed code and high trust
Any programming language can be used
Data Storage Locations: SharePoint Online, Content Database
Data Storage Locations: ISV Storage, Azure Storage, Content Database.
Can be hosted on either SharePoint on-premises or office 365
Deployed outside the SharePoint.
Business logic is mainly remote server-side code.
SharePoint add-in model does not allow managed code to be installed directly on SharePoint, however it can be hosted in application server and a separate website (eg. on IIS) on in azure.
App usage scenario: An add-in that includes a people picker control and that stores information about SharePoint users in a SharePoint list
App usage Scenario: Can be used in situations where SharePoint being consumed as service and/or hosted by a provider. App model is the option if you do not have a on premises installation. Go with this option when you require server-side managed code.
App Components are SharePoint components like SP Features, Custom Actions, Lists, Site Columns, Content Types, BCS models(web scoped), Web and list templates
Can connect to any internal or public web service
SharePoint-hosted SharePoint Add-ins do not support event handling,
To handle list and list item events, you need to create remote event receivers (RERs), which are web services that run externally to the SharePoint farm or SharePoint Online.
This add-in components are hosted in the isolated add-in domain of your SharePoint farm
Can be hosted in any web server or hosting service
Authentication: This uses the privileges of the signed in user
CRUD Operations: You can use either the REST/OData web service or one of the client object models in SharePoint 2013.
SP.js is available to perform create, read, update, and delete (CRUD) operations on SharePoint data.
CRUD Operations: You can use the REST/OData endpoints in SharePoint 2013 to perform create/read/update/delete (CRUD) operations on data in the add-in web. You can write server side code any technology you like to perform this CRUD operations.
These apps don’t work with SAML Claims authentication provider with ADFS 2.0
Any SharePoint component that can be in a SharePoint-hosted add-in can also be in a provider-hosted add-in.