In numerous projects I have seen development environments that resemble nothing like production. Only to result in a problematic transition through the ALM process, bugs caused by inconsistency, significant differences in SharePoint updates, configuration and even permissions.
I am not saying that you shouldn’t write your app to “expect a specific configuration” or to avoid best practices around handling configuration issues. However, to reduce issues down the line, as a minimum, environments should be setup with the following:
On May the 4th Microsoft announced a new development framework for SharePoint, based on pure client side technologies. This framework would be utilising a combination of Node.js, Gulp, TypeScript, React and Knockout. It marked a radical change to the way we develop apps using established open source frameworks for pure client side with SharePoint office 365 and eventually SharePoint 2016.
Yesterday (18th August) Microsoft announced the release of SharePoint framework in Preview: See announcement: SharePoint Framework Developer Preview Release. So we are going to create a new app with this framework.
This summer is looking like an awesome period for new development features and the Office PnP team recently published a web cast on SharePoint Web Hooks in Office 365, although this is not yet released, the public preview for first release tenants will be due this summer.
So what are Web Hooks?
Web Hooks are an asynchronous push mechanism to provide notification to a remote endpoint for changes. In the context of SharePoint, this would be similar to Remote Event Receivers that trigger a remote call when changes are made to the subscribed resource i.e. lists or web.