Developing with SharePoint
Framework (SPFx) on-premises
Dragan Panjkov
Dragan Panjkov
Microsoft MVP: Office Servers and Services; Office Development
Consultant at K2 Northern Europe (www.k2.com)
Website and blog: www.dragan-panjkov.com
Twitter: @panjkov
Github: www.github.com/panjkov
Agenda
• SharePoint Framework?
• On-premises limitations
• What is supported where
• Configuration steps
• Demos
SharePoint UX – Evolving cross versions
2009
SharePoint
Server 2010
2006
Office SharePoint
Server 2007
2003
SharePoint
Portal Server 2003
2001
SharePoint
Portal Server 2001
2012
SharePoint
Server 2013
2016 …
SharePoint
Server 2016, SPO
SharePoint Framework Extensibility Principles
SharePoint Framework
Web Parts
SharePoint web parts
Extensions
extend the SharePoint user experience within modern pages and
document libraries
• Application Customizers
• Field Customizers
• Command Sets
Understanding differences
• SharePoint Online is always latest version
• All new Features are introduced here
• SharePoint on-prem version is a fork
• Feature Freeze
• New Features added through Public Updates ( September 2017 PU – FP2 for
SP 2016)
• Cannot check/ensure version of server side dependencies
• Yeoman Generator is using packages actual at moment when fork is
created (mostly)
Considerations
• SharePoint App infrastructure is still necessary
• App Management Service
• Subscription Settings Service
• APP URLs
• App Catalog
http://www.mikerodionov.com/2016/09/provisioning-sharepoint-app-
catalog-in-sp-20132016/
SharePoint 2016
• SharePoint Framework Web parts on Classic Pages
• Using version 1.1 of libraries
• Available as a choice since Yeoman Generator v1.3
• Necessary to host JavaScript and JSON files somewhere
• If SP document library is used – JSON file type has to be unblocked
SharePoint 2019
• Modern Pages
• Modern Sites
• Extensions
• Webhooks
• No CDN is required
• Column formatting
• Tenant scoped deployment
• ALM APIs
https://developer.microsoft.com/en-us/sharepoint/blogs/sharepoint-dev-
community-pnp-general-sp-dev-sig-recording-15th-of-november-2018/
Resources
• aka.ms/spfx
• http://www.mikerodionov.com/2016/09/provisioning-sharepoint-
app-catalog-in-sp-20132016/
• http://jenkinsblogs.com/2016/10/04/deploy-spfx-client-side-web-
part-to-a-sharepoint-library/
• www.dragan-panjkov.com
• https://developer.microsoft.com/en-us/sharepoint/blogs/sharepoint-
dev-community-pnp-general-sp-dev-sig-recording-15th-of-november-
2018/
Developing with SharePoint Framework (SPFx) on-premises

Developing with SharePoint Framework (SPFx) on-premises

  • 1.
    Developing with SharePoint Framework(SPFx) on-premises Dragan Panjkov
  • 3.
    Dragan Panjkov Microsoft MVP:Office Servers and Services; Office Development Consultant at K2 Northern Europe (www.k2.com) Website and blog: www.dragan-panjkov.com Twitter: @panjkov Github: www.github.com/panjkov
  • 4.
    Agenda • SharePoint Framework? •On-premises limitations • What is supported where • Configuration steps • Demos
  • 5.
    SharePoint UX –Evolving cross versions 2009 SharePoint Server 2010 2006 Office SharePoint Server 2007 2003 SharePoint Portal Server 2003 2001 SharePoint Portal Server 2001 2012 SharePoint Server 2013 2016 … SharePoint Server 2016, SPO
  • 6.
  • 7.
  • 8.
  • 9.
    Extensions extend the SharePointuser experience within modern pages and document libraries • Application Customizers • Field Customizers • Command Sets
  • 10.
    Understanding differences • SharePointOnline is always latest version • All new Features are introduced here • SharePoint on-prem version is a fork • Feature Freeze • New Features added through Public Updates ( September 2017 PU – FP2 for SP 2016) • Cannot check/ensure version of server side dependencies • Yeoman Generator is using packages actual at moment when fork is created (mostly)
  • 11.
    Considerations • SharePoint Appinfrastructure is still necessary • App Management Service • Subscription Settings Service • APP URLs • App Catalog http://www.mikerodionov.com/2016/09/provisioning-sharepoint-app- catalog-in-sp-20132016/
  • 13.
    SharePoint 2016 • SharePointFramework Web parts on Classic Pages • Using version 1.1 of libraries • Available as a choice since Yeoman Generator v1.3 • Necessary to host JavaScript and JSON files somewhere • If SP document library is used – JSON file type has to be unblocked
  • 14.
    SharePoint 2019 • ModernPages • Modern Sites • Extensions • Webhooks • No CDN is required • Column formatting • Tenant scoped deployment • ALM APIs https://developer.microsoft.com/en-us/sharepoint/blogs/sharepoint-dev- community-pnp-general-sp-dev-sig-recording-15th-of-november-2018/
  • 15.
    Resources • aka.ms/spfx • http://www.mikerodionov.com/2016/09/provisioning-sharepoint- app-catalog-in-sp-20132016/ •http://jenkinsblogs.com/2016/10/04/deploy-spfx-client-side-web- part-to-a-sharepoint-library/ • www.dragan-panjkov.com • https://developer.microsoft.com/en-us/sharepoint/blogs/sharepoint- dev-community-pnp-general-sp-dev-sig-recording-15th-of-november- 2018/