7. Is all SP Online 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
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
14. Upload static assets
• JSON source file
• Manifest for webpart
• JS Files
• Minified version of your code
• Localized strings
• Located in /temp/deploy folder
40. Enable the SharePoint CDN 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
49. SharePoint
Application
Lifecycle
Management
• Add SharePoint Framework 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.
52. I developed a SharePoint Framework solution,
what to do next and how to install it automatically?
Yannick Borghmans
Notes de l'éditeur
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
Built into the SharePoint mobile apps
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: