6. Agenda
• Introduction
• Demo – the pirates treasures
management solution
• History
• The new stack
• Provisioning
• Missing bits
• Accessing data
• Line of business applications
• Batch jobs
• Conclusion
10. SharePoint Full Trust
• Code executing server side
• User or service Context
• Bad code would break/slow
down SharePoint
• Deploying meant downtime
• Very little unit tests
11. SharePoint Sanbox
• Still running on SharePoint server
• User Context only
• Bad code would not impact SharePoint too much
• No downtime during deployments
• Still no unit tests
• Limited access to OM
• Bad throttling could happen
• No more batch jobs
12. SharePoint add-ins (SharePoint Hosted)
• Running client-side
• User Context only
• Bad code doesn’t impact SharePoint
• But wait, wireframe!!
• No downtime during deployments
• Still no unit tests
• Incomplete REST API
• Still no more batch jobs
13. SharePoint Add-ins (Provider Hosted)
• Running Server Side (not SharePoint)
• User and App Context
• Bad code doesn’t impact SharePoint
• No downtime during deployment
• Unit tests got easier
• CSOM and REST API
• Batchjobs « capable »
27. No feature framework with SPFX
• Most SPFX samples include code provisioning
• SPFX roadmap doesn’t include provisioning
• Pattern and Practices has made awesome work
• PnP Provisioning far better than code
30. Multiple API’s
• SharePoint REST API’s
• TypeScript libraries available, use those!
• Microsoft Graph
• Get access to much more data
• (no demo on that today, too much content)
• (Microsoft working on improving auth story)
31. Reacting on data events
• We used to have Event Receivers
• SP Provider Hosted Add-ins have RER’s (same thing over HTTP)
• SharePoint API /MS Graph provides webhooks support
42. Modern tools reference
Purpose Workflows Forms LOB Batch Provisioning Branding Data Events …
Old tool SP Designer InfoPath Front
end
scripting
TimerJob Feature
Framework
Design
manager
SSOM/
JSOM
Event Receivers …
New
tool
Flow/
Logic Apps
PowerApps SPFX Azure
Function
PnP
Provisioning
SPFX in the
future *
CSOM/
PNP-Core/
REST/
Graph
RER’s
WebHooks
…
43. Conclusion
• We have a modern tooling
• The SharePoint Framework is one item of our pirate gear
• Add-ins are still relevant in some scenarios
• Leverage other tools to have a full spectrum
• SharePoint dev cost will decrease because bigger community
• SharePoint devs’ life just became better
• Happy coding
Gestion des questions, interaction, ok avec ce programme?
1 powerapps desktop, treasures, fill in treasure
2 show the list item in sharepoint https://baywet.sharepoint.com/sites/sessionmigratespfx/Lists/Treasures
3 show the tweet on my profile
4 show the webpart on workbench https://baywet.sharepoint.com/sites/sessionmigratespfx/_layouts/15/workbench.aspx
5
Show the solution in code, gulp serve https://baywet.sharepoint.com/sites/sessionmigratespfx/_layouts/15/workbench.aspx
gulp --tasks