Get an introduction to why we need a CDN with SPFx, and Office365 CDN versus your custom CDN.
Those files come from a CDN. When you deploy a web part in a typical SharePoint site, that web part is going to https download the actual running files from a CDN. It has to be https. So, we need a CDN. We have two choices for CDN. One, you can use your own CDN. This is just an https URL, but certainly you can leverage an Azure CDN, if you need more features.
The disadvantage of that approach is that you have to modify your SharePoint Solution package before you can package it and deploy it. The URL for your CDN gets embedded in the final deployable artifact. The better approach is to simply use the Office 365 public CDN. The advantage of going with the public CDN is that you can just upload and deploy the SharePoint Framework solution, and during the installation, all the necessary files automatically become available, as long as the tenancy has the CDN enabled.
I will be showing you both of these approaches, but we're going to use the Office 365 CDN for both. However, in one scenario I will control all the URLs, and in the second scenario we will have SharePoint Framework dynamically generate the URL for me. Let's dive into some demos.
- Setting up a document library to act as a CDN
- Managing the Office 365 CDN using PowerShell and the Office 365 CLI
- Enabling or disabling the site collection app catalog
- Upgrading SPFx solutions
- Application lifecycle management (ALM) APIs