React Component Life Cycle

What is your favorite technical article?

For me, Understanding ASP.Net View State is my all time favorite article. I might have read it hundred's of times. It helped me all my career as a dot.net & sharepoint developer.

so, when we have our basics clear, complex tasks will be easy to handle. So the same applies for REACT as well.

Example: 
I have recently worked on a SPFX webpart integration with JqueryUI.

React Component Basics

For this post , i assume you are familiar with basics of SharePoint framework development, using yoman templates , node package manager and gulp. Else please refer to my earlier post Basics of SPFX

Sharepoint Framework (SPFX) is becoming popular as it is the only way to add custom functionality to a Sharepoint Online modern pages.

We can integrate any java script framework to work with SPFX. In last post we did integrate Angular with SPFX.  But, we need to do everything from scratch like importing packages and then adding them in config files, etc.

REACT is one of the java script framework which comes with yoman scaffold out of the box. So the installation, references and default code were taken care by yoman generator. React got lot of plugin support and its consistently improving by each version.

So REACT became a mandatory component to learn for SPFX development.

REACT coding is mostly dealing with properties and state on client side. 

For this we have 2 types of components in REACT.

Basics of Angular SharePoint Framework Webpart

When you search angular sharepoint framework, you gonna encounter the "ToDoApplication". Let me tell you that is not an example suitable for a beginner to understand how to integrate angular with sharepoint framework.

Objective: Create a sharepoint framework webpart from scratch and integrate it with angular framework.

So to begin with, i assume you are aware of basics of angular and sharepoint framework. If not you can checking below mentioned articles before this article.

AngularJS : Basics

Basics of Sharepoint Framework Webparts

Basics of Sharepoint Framework Webparts

This post is intended to share my knowledge on basics of sharepoint framework webparts.
Below are the tasks we address:

1. Why sharepoint framework (SPFx).
2. How to setup a machine for it
3. How to develop your first SPFx webpart
4. How to deploy it to your SPO.
5. How to Consume it on client SPO site.
6. How to upgrade your SPFx app/webpart.

Sharepoint Online Tabular Custom Search Display

         We know search is becoming sophisticated in newer versions of SharePoint. But still all clients are not fond of the OOTB search results display. So in this post we see how to transform Sharepoint Online search results into Tabular display using Display Control templates, Display item templates and Hover panel templates.

Note: We are dealing with "Search Results webpart" in this post, not the "Content search webpart" for search results display.

Objective: 

Transform this display

 into this display

It is my first try of doing this, and it is not a straight forward thing.

SharePoint Online Search Basics

          If you are a SharePoint 2010 Developer and trying to figure out how search works in Sharepoint Online, this is for you. As i am one of you and like i said in my first post on my blog, the content is not to show what i know, but to share what i have learned.

         We will refer to 2010 concepts like "Managed Properties", "Content Sources", "Search Scopes", "Search Result webparts" and see how we going to achieve the same results in Sharepoint online.

        Before you jump into solutions / development, you should know how things were changed from SP2010 to SP Online. You (Admin) used to manage everything in Sharepoint On-Premises from Central Admin, but not in SP Online. Below image will depict what will be your responsibility as a Global administrator of your tenant.

        Looking at the Admin portal of your tenant, you may figure out that you cannot do everything you can do in SP2010 Central Admin.

AngularJS : Basics

I know i am bit late to the AngularJS party, but better late than never, right !

Before we get into writing code , let me tell you i am also learning AngularJS and i know the state of a newbie's mind when you try reading this post. So i assume no prior knowledge of Angular on user front.

If you are a star developer working with angular service factories, may be this is too basic for you.
Hey, nothing wrong in checkup on basics, right !

Objectives:
                  1. Why angularJS
                  2. Learn basics - module, controller , data binding

async and await in .Net Framework 4.5

Let me start with the difference between synchronous process and asynchronous process.

As the above image depicts, we usually consider asynchronous process in case of a time taking task. Making an asynchronous call, we will execute the tedious task on a separate thread and will continue with remaining process on initial thread. Thus we will be able to execute both the tasks paralelly.

Until now we have been using a standard process of calling a function or method asynchronously.
Until .Net framework 4.0 below is the typical process of executing a method asynchronously.

I created a small sample application  in Visual Studio 2013.
Before we go into more details, i would like to highlight a simple fact.

"Until .Net Framework 4.0 we call a non-asynch method asynchronously, but from .Net Framework 4.5 we have asynch methods which reduces lot of efforts in development perspective."

Query Rules - Beyond Search box in Sharepoint 2013

Developers often excited about new technology like EF6.0, C#5, Visual Studio VNext, MVC 6, Sharepoint 2013, Cloud platform. But they put the most important fact on the blind side "What features of this new technology we use?"

Don't you think that defeated the purpose of having a car instead of cart.

Whats the point of using SharePoint 2013, if we din't use any new features provided by it. Right?

Azure Web Sites, Cloud Services and Virtual Machines comparison

This post is completely consumed from Microsoft Azure site . . . But i found this information really useful and would like to archive on my blog as well.

Azure offers several ways to host your web applications, such as Azure Web Sites, Cloud Services, and Virtual Machines. After looking at these various options, you might be unsure which one best fits your needs, or you might be unclear about concepts such as IaaS vs PaaS. This article helps you understand your options and helps you make the right choice for your web scenario. Although all three options allow you to run highly scalable web applications in Azure, there are differences which can help guide your decision.

In many situations, Azure Web Sites is the best option. It provides simple and flexible options for deployment and management, and it is capable of hosting high-volume web sites. You can quickly create a new web site with popular software, such as WordPress, from the Web Application Gallery, or you can move an existing web site to Azure Web Sites. Using the Azure WebJobs SDK (currently in preview) you can also add background job processing.

You also have the option to host web applications on Azure Cloud Services or Azure Virtual Machines. These options are good choices when your web tier requires the additional level of control and customization that they provide; however, this increased control comes at a cost of increased complexity in application creation, management, and deployment. The following diagram illustrates the trade-offs among the three options.