Jean Paul's Blog

There are 2 types of People in the World, One who Likes SharePoint and..

  • Microsoft MVP

  • MindCracker MVP

  • CodeProject MVP

  • eBook on SharePoint 2010

  • eBook on Design Patterns

  • eBook on Windows Azure

  • NLayers Framework @ CodePlex

  • MSDN Forums

  • .Net vs. Java

    Due to Public Demand
  • Advertisements

Archive for the ‘SharePoint 2016’ Category

SharePoint Framework – New SharePoint 2016 Development Model

Posted by Paul on September 27, 2017

SharePoint Framework (SPFx) was introduced in early 2017 and it is the Preferred Development Method for SharePoint 2016 and SharePoint Online.

Image result for sharepoint framework

Advantages of SPFx

  • Page and Web Part Model – No IFrame so increased performance
  • Runs in context of Current User – better context permission accessibility
  • Responsive Controls – easier rendering in mobile & tablet devices
  • Full-fledged JS support – easier integration of React, Angular frameworks
  • Free web parts – faster development on common scenarios

History of SharePoint Development Models

As an early starter with SharePoint, I would like to list down the SharePoint Development models from my mind.

Farm Solutions

This was the Initial development world.  It consisted of C# code in DLLs running in the server-side.  Later this led to issue of Full Trust and Poor code affecting whole server.

SharePoint 2003, 2007, 2010, 2013 had full support for Farm Solutions.

Sandboxed Solutions

Then came the Sandboxed Solutions which tried to resolve some of the Farm Solution issues.  Sandboxed Solutions set Trust configuration, Restricted Code, Quota Limit there by preventing a Poor Code from hampering server.  Still the code runs in Server-side leading to performance issues when a large number of users using a Dashboard web part for example.

Here the C# code will be executed on SharePoint server.

SharePoint 2007, 2010, 2013 had support for Sandboxed Solutions.


Client-Side Object Model (CSOM) was developed to address few of the Sandboxed Solution issues.  CSOM still uses C# code but can be executed outside the SharePoint server.  This freed up the SharePoint Server from unwanted loads and also relaxed on the Deployment overheads with just referring to Client Side DLLs.

SharePoint 2010, 2013 supported CSOM.


JavaScript Object Model (JSOM) bought the Client Side Object Model advantage to the SharePoint pages.  Here the JavaScript code will be executed in the Client browser there by Freeing up Server Performance cycles. 

JSOM also supported Batching which was earlier boon to reduce server roundtrips.

The initial way of executing JavaScript was attaching code file with a Script Editor web part.  Later JSOM usage evolved as Solid Client Side Applications through usage of Angular, React and other JavaScript frameworks.

SharePoint 2010, 2013 supported JSOM.


Apps (Now Add-ins) was introduced in SharePoint 2013 to package & publish complete applications to Corporate or Office 365 store.  In this way the client side support was extended to business level.   Apps came with SharePoint Hosted Apps (SHA) initially.

Apps also provided PHA (Provided Hosted Apps) which allow running C# code in outside servers.

Apps were using IFrame and thus cause redirection & page load delays.

SharePoint 2013, 2016 supported Apps.


SharePoint Framework (SPFx) was introduced in SharePoint 2016 to address the problems with Apps.  There are No IFraames thus increasing the Page Performance.  SPFx also comes with ready made reusable web parts for common functionalities.

SharePoint 2016 supports SPFx.



Posted in SharePoint, SharePoint 2016 | Tagged: , , | Leave a Comment »

Webhooks in SharePoint 2016

Posted by Paul on July 28, 2017

SharePoint 2016 introduced Webhooks for List Event Handling.  Webhooks are much better than Remote Event Receivers.


Webhooks are enabled on SharePoint list items

Webhooks allow developers to Subscribe list item changes

Webhooks support only Asynchronous events

Webhooks requires a Target URL


You need an Office 365 Subscription to test Webhooks.

You need to create a List Event subscription on the required List

You need to setup a Server URL to host the Webhook URL

Subscription can be enabled with an Expiration Date


The class need to be inherited from SPWebhookNotification class.

The class should implement properties for SubscriptonId, ClientState etc.

Http Post attribute should be used for the receiver method.

Posted in SharePoint, SharePoint 2016 | Tagged: , , | Leave a Comment »

SharePoint 2016 New Features

Posted by Paul on May 13, 2015

In this article I would like to highlight the features of SharePoint 2016. This information was collected from the Ignite session conducted by Microsoft.


Release by 2016-Q2

SharePoint 2016 is expected to release by 2016-Quarter-2.


Look N Feel

I cannot find any huge difference in SharePoint 2016 Look N Feel. The Tiled UI will be continuing.


On-Premise is here to Stay

Microsoft promised SharePoint 2016 will be having On-Premise version. There was a rumor about discontinuing On-Premise version from 2016 onwards. But, customers have reasons for all data cannot be on SharePoint Online.

Search with Delve

SharePoint 2016 will be having Search with Delve app. Delve is a new way of searching & presenting contents based on user’s interest. Delve’s roots goes to Office 365.

Delve can present information from Exchange, OneDrive for Business, SharePoint Online and Yammer based on user’s interactions. Please find references section to learn more about Delve.

Farm Solutions will be supported

Farm Solutions will be supported. This should enable lot of 2010 & 2013 code to be migrated to 2016 with least amount of upgrade to CSOM. But, as said earlier App Model / CSOM will be the preferred development model.


SharePoint 2016 will have improvised support for OneDrive. This is part of Microsoft’s Hybridization movement for On-Premise.

Hybridization is bringing cloud-features to On-Premises, rather taking On-Premise customers to Online versions.


Yammer will be integrated with SharePoint 2016. This is also part of Microsoft’s Hybridization movement for On-Premise. Additionally, External User interaction will be added to Yammer to enable external-users like customer/vendor communications.

Office Graph

Office Graph is the core component which will enable Delve Search & Hybridization feature. But, Office Graph will be residing in SharePoint Online and a Hybrid Connectivity from SharePoint 2016 will be provided.

Responsive UI

There are improvements to the default responsive user interface. This enabled SharePoint 2016 better view ability in mobile devices.

Hardware Requirements

It is cooler to see that the hardware requirements will be similar to SharePoint 2013. This will save lot of $ for developers & administrators who recently invested in hardware for SharePoint 2013.

Online Patching

Administrators should really like this feature. SharePoint 2016 allows applying patches while being Online. No need to take the servers off & users can continue working while patches are applied. Zero Downtime!

Expanding Boundary Limits

SharePoint 2016 expanded boundary limits on content database size, list view items count etc. This should save lot of shredding-jobs from Administrators and Developers.

User Profile Service Application will be removed

User Profile Service Application will be removed. I am not clear about the details on Active Directory synchronizing and so. Will have to play with the preview version to understand this.



Roadmap for Delve

SharePoint Evolution


In this article we have explored SharePoint 2016 features overview.

Posted in SharePoint, SharePoint 2016 | Tagged: , , | Leave a Comment »