Download to read offline
More Related Content
Similar to SPSCasablanca - SPFx Deployment
![5G Explained! A High Level Overview [Introduction]](https://cdn.slidesharecdn.com/ss_thumbnails/5gexplainedahighleveloverview-260119165306-cc137a3e-thumbnail.jpg?width=640&height=640&fit=bounds)
SPSCasablanca - SPFx Deployment
- 1. I developed aSharePoint Framework solution, what to do next and how to install it automatically? Yannick Borghmans
- 2. yannickborghmans.com Linkedin.com/in/yborghmans @yborghmans Yannick Borghmans Office 365/SharePointTechnical Lead @Ventigrate
- 3. Agenda Building SPFx Deployment SharePoint Azure Appcatalog ALM API
- 4.
- 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. Is all SPOnline development in JavaScript? No In similar ways as with SharePoint Add-in model, server side development is needed for back end services SharePoint Framework concentrates on user interface, not on fundamentals around the API usage
- 8. • Tooling • Node.js •Yeoman • Gulp • TypeScript • Visual Studio (Code) • Frameworks – Choose yours • React • Angular.js • Knockout • Etc. Typical tooling for SharePoint Framework
- 9.
- 10. Client-side Web PartBuild Flow
- 11. Package your webpart •Use the bundle gulp task to build, localize, and bundle the project • Use the package-solution gulp task to package the project into a .sppkg file • The ship parameter build task creates a minified version of the bundle and copies all of the web part assets
- 12.
- 13. Deploy App tothe SharePoint App Catalog
- 14. Upload static assets •JSON source file • Manifest for webpart • JS Files • Minified version of your code • Localized strings • Located in /temp/deploy folder
- 15. Install the app •Go to your SharePoint Site • Add an app
- 16. Add the webpart to a SharePoint page • Create a page on your Office 365 site • Add the web part to the page
- 17.
- 18.
- 19. Update SPFx solution •Upgrade version (./config/package-solution.json)
- 20. Update SPFx solution •Gulp clean (optional) • Gulp bundle --ship • Gulp package-solution --ship • Upload to app catalog & upload static assets (.js, .json)
- 21. Update SPFx solution •No need to update app on sites => webparts are automaticaly using the latest code
- 22.
- 23. Deploy possibilities SharePoint Document library Clientside assets Office 365 CDN Azure CDN Extra Tenant deploy
- 24. What defines thehosting location?
- 25.
- 26. SharePoint – documentlibrary • Create a document library • Create a folder/solution you want to host
- 27. SharePoint – documentlibrary • Update the CDNBasePath in write-manifest.json
- 28. SharePoint – documentlibrary • Upload app package to app catalog
- 29. SharePoint – documentlibrary • Upload .js files to document library
- 30. SharePoint – documentlibrary
- 31. Client side assets Introducedin SPFx v1.4 to include static assets in .sppkg file
- 35.
- 36.
- 37.
- 38. Office 365 -CDN
- 40. Enable the SharePointCDN origin • Open the SharePoint Online Management Shell • Execute the following Powershell commands to enable the CDN, set the CDN origin, and return the CDN Origin ID
- 42.
- 43. Tenant deploy Introduced inSPFx v1.4
- 47. SharePoint Application Lifecycle ManagementAPI API to manage the deployment of your SharePoint Framework solutions
- 49. SharePoint Application Lifecycle Management • Add SharePointFramework solution or SharePoint Add-in to tenant app catalog. • Remove SharePoint Framework solution or SharePoint Add-in from tenant app catalog. • Enable SharePoint Framework solution or SharePoint Add-in to be available for installation in tenant app catalog. • Disable SharePoint Framework solution or SharePoint Add-in not to be available for installation in tenant app catalog. • Install SharePoint Framework solution or SharePoint Add-in from tenant app catalog to a site. • Upgrade SharePoint Framework solution or SharePoint Add-in to a site, which has a newer version available in the tenant app catalog. • Uninstall SharePoint Framework solution or SharePoint Add-in from the site. • List all and get details about SharePoint Framework solutions or SharePoint Add-ins in the tenant app catalog.
- 50.
- 51.
- 52. I developed aSharePoint Framework solution, what to do next and how to install it automatically? Yannick Borghmans
Editor's Notes
- #6 Tahoe/SPS 2001 – ASP Based, Single Box SP 2003 – Moved to ASP.NET, scale out, enterprise manageability SP 2007 – Added ECM, Publishing, Shared Services SP 2010 – FAST acquisition, search driven portals, scaled up doclibs SP 2013 – Multitenant, base for our cloud based release SP 2016 – First version migrated back from Cloud
- #7 Built into the SharePoint mobile apps
- #9 SharePoint will also support open source tooling to drive greater efficiencies when developing Parts and Apps. These tools should not be considered a replacement of an organizations traditional tools, but rather an extension of those, providing new opportunities to quickly get up and running with SharePoint development. If you’re familiar with Visual Studio development with SharePoint, this tools carry a lot of similarities with the tools you may already be familiar with for example:
- #41 Connect-SPOService -Url https://ventigratedev-admin.sharepoint.com/ -Credential $creds https://ventigratedev.sharepoint.com/sites/app/ClientSideAssets