The document introduces the SharePoint Framework as a new approach for developing customizations for SharePoint. It summarizes the limitations of previous development models like farm solutions and add-ins. The SharePoint Framework allows customizations to run within the permissions of the current user and uses open source tools and libraries with an industry standard development model. It leverages common web development tools like Node.js, Yeoman, Gulp and TypeScript rather than traditional Microsoft tools. Customizations are developed as client-side web parts with a defined build flow to package and deploy solutions.

1. Copyright© 2012 Microsoft Corporation
Introduction to the
SharePoint Framework
Don Kirkham
Lead Collaboration Architect
MCPD: SharePoint, MCT
Don.Kirkham@GMFinancial.com
DonKirkham@live.com
@DonKirkham

2. Copyright© 2012 Microsoft Corporation
Agenda
Intro/Poll
Overview of
Dev Models
New Tools
and Process

3. WSPs
• Farm solutions only
supported in on-premises
• Only declarative sandbox
solutions supported in
SharePoint Online
• Requires deep knowledge
on SharePoint internals
(xml structures)
Add-ins
• Decoupling
customizations from
SharePoint
• Provides security model
for the customization
permissions
• Limited web part
experience as add-in part
• Additional operational and
maintenance requirements
External apps / SPAs
• Decouples customizations
from SharePoint
• Bring your own technology
stack
• Provides security model
for customization
permissions
• Requires custom
implementation of user
interface
SharePoint Framework
• Customization runs as part
of the SharePoint page
• Flexible web part
experience
• Runs under permissions of
current user
• Industry standard
development model
Characteristics
Flexibility
Cost impact
(short and
long term)
Support
in cloud
SharePoint development options
Fair Good ExcellentLimited

4. SharePoint Framework
• Advantages
• Customizations are executed in the
context of the SharePoint page
• No complex permission model
• Consistent user experience
• Cross platform development
• Native support cross different devices
• Supports open source tooling and
libraries
• Industry standard development models
• On-premise support coming
• Disadvantages
• Runs with the permissions of the end user
without additional permission model
• Introduces completely new development
model for SharePoint with new tools and
libraries to use
• Requires new guidance and policies for
development processes

5. • Tooling
• Node.js
• Yeoman
• Gulp
• TypeScript
• Visual Studio (Code)
• Frameworks – Choose yours
• React
• Angular.js
• Knockout
• Etc.
Typical tooling for SharePoint Framework

6. Web stack tooling compared to classic MS tools
IIS Express
VS Project →
New → <Template>
C#
MS Build

7. Client-side Web Part Build Flow
gulp package-solution --ship
gulp deploy-azure-storage
manual upload of the app

9. Q&A

10. aka.ms/OfficeDevPnP