Integration of GitHub and GitFlow with SourceTree

I have an experience using Source Tree with Mercurial.

We can use Source Tree to use GitFlow with UI instead of firing commands in command prompt.

Reference links:

1. How to use Source Tree with GitHub – (https://www.youtube.com/watch?v=YwekKdd79lk)
2. Git Flow Part 2 – Using Git Flow in Source Tree Tutorial (https://www.youtube.com/watch?v=z53JJ7P78Vc)

Download Source Tree for Windows : https://www.sourcetreeapp.com/

This is an example screenshot how it will display with the use of Source Tree. Actions like Crate Feature, Create Release and Create Hotfix branch are done using GitFlow.

Source Tree with GitFlow
Please follow and like us:

Google+ API going to be Shutdown

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:

Google+ integration with mobile and web is also going to shutdown.

As a part of the feature Google Sign in feature is available and they are trying to provide a new visual change for the enterprise organizations.

You can find more details on their blog: https://developers.google.com/+/api-shutdown

Please follow and like us:

Import Info Path form to the SharePoint Online

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

 

 

 

Please follow and like us:

Comparison between SharePoint Hosted and Provider Hosted App

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.

 

SharePoint Hosted Provider Hosted
No server side code, 100% client side code Managed code and high trust
Can be developed using HTML5, CSS, JavaScript, jQuery, ASP.NET Ajax, CSOM, REST API, Silverlight, KnockOut JS, Angular JS Any programming language can be used
Data Storage Locations: SharePoint Online, Content Database Data Storage Locations: ISV Storage, Azure Storage, Content Database.

(ISV – Independent Software Vendors)

Start Page Location: On-Premises, SharePoint Online Start Page Locations: ISV Hosted web site, SharePoint Online, On-Premises SharePoint Online, On-Premises
Can be hosted on either SharePoint on-premises or office 365 Deployed outside  the SharePoint.
Business logic is JavaScript on custom SharePoint pages 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 Authentication: Uses OAuth or the JavaScript cross-domain library
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.
Please follow and like us:

Microsoft Azure – Automate Creating, Developing and Deploying Azure Websites

Microsoft Azure is a quick and easy way to create and deploy Web sites or APIs for your cloud consumers. Much has been written on different aspects of Azure Websites, including security, deployment and so on. It’s always a challenge to bring this information into a real-life implementation. In this article, I’ve pulled together these various facets to help you quickly create a production-ready Azure Website. I’ll walk you through the end-to-end lifecycle of creating, deploying, configuring and monitoring an Azure Website.

Refer this MSDN link for more details :
https://msdn.microsoft.com/en-us/magazine/dn948107.aspx

Courtesy : Gyan Jadal

Please follow and like us:

Enjoy this blog? Please spread the word :)