The New SharePoint Framework

Prepared by: Chris Buchanan & Vili Bogdan

1

Agenda

• Evolution of SharePoint Development

• What is the SharePoint Framework

• Advantages of the new framework

• Prerequisites for using the framework

• Hello World Web Part Workshop

• Resources

3

Evolution of SharePoint Development

Full Trust/Farm Solutions They still get the job done

Currently the only feasible way to perform certain tasks

React in real-time to events (event receivers)

Still heavily used by MS SharePoint team

Still heavily used by third-party vendors (AvePoint, Metalogix, Nintex, etc.)

but…

Highest risk of destabilizing the farm

No cloud use

No-code Sandboxed Solutions Very limited in functionality

Rarely used “in the wild”

“Design Manager” saves designs as sandboxed solutions

Are supported in O365

SharePoint Add-ins

Microsoft’s first take at enabling modern development techniques

Vendors/developers can make their apps available in a store

Supports elevation of privileges through app-only rights

Still very much relevant and not going away

SharePoint Framework Microsoft’s attempt to enable

using the latest technologies (a.k.a. what the cool kids use)

Cross-platform development Windows, Linux or Mac OS X

Runs in user context

Very early stages – Developer preview

Aug 17, 2016 – Drop 1

…

Nov 22, 2016 – Drop 6

Currently can only build client side web parts

First version supposed to be release in early 2017

8

Evolution of SharePoint Development

9

What is the SharePoint Framework?

Check this out: https://blogs.office.com/2016/05/04/the-sharepoint-framework-an-open-and-connected-platform/

10

11

Advantages of the New Framework

Gives a more “railed” experience to extending SharePoint using client side development

Less risk of MS updates breaking your customizations

SEWP could be removed by end-users, breaking functionality

Hooks when page loads/renders

Tooling allows for rapid dev

Ability to enhance the out of box experience.

No need to recycle the application pool to deploy solutions.

Mobile friendly

Allows developers to more easily transition onto SharePoint Intranet or Portal Projects or build out custom web parts without having to have more than a background in Web Development.

The SharePoint Framework is open and there won’t be any secret development approaches for Microsoft who will be eating their own dogfood.

Hosted and run identically in O365 and on premise*

12

Advantages of the New Framework

Runs in the context of the current user and the connection in the browser

No Iframes

Controls rendered in the normal DOM

Controls are responsive & accessible*

Dev access to full lifecycle

Rendering

Load

Serialize / deserialize

Configuration changes

Front end web framework agnostic*

Toolchain based on open source client dev

Reliable performance

Solutions are deployed as web parts on

Modern pages

Publishing pages

Classic pages

The biggest challenge?

Getting started!

Tool Comparison

IIS Express

Project

Templates

15

Pre-Requisites

Node.Js

NPM (Node Package Manager)

Gulp / Webpack

AngularJs / KnockoutJs / ReactJs

Typescript

Karma and Jasmine

Microsoft Graph / SharePoint REST API

16

Hello World Workshop

17

Resources Getting Started

https://github.com/SharePoint/sp-dev-docs/wiki Get Started section, starting with “Setup your Machine”

Channel 9 Getting Started Tutorialhttps://channel9.msdn.com/blogs/OfficeDevPnP/SharePoint-Framework-Tutorial-1-HelloWorld-WebPart

Microsoft SharePoint BlogThe Future of SharePointhttps://blogs.office.com/2016/05/04/the-future-of-sharepoint/

SharePoint Framework – A beginners a Guidehttp://sivarajan.me/post/SharePoint-Framework-A-Beginner-series-for-SharePoint-developer

SPFx Web Part samples and tutorialshttps://github.com/SharePoint/sp-dev-fx-webparts

Using Visual Studio 2015 instead of VS Codehttp://weshackett.com/2016/07/the-future-of-sharepoint-paradigm-series-using-visual-studio-2015-to-build-a-sharepoint-framework-client-web-part/