From the course: SharePoint Framework for Developers: 3 Deployment, Upgrades, and Lifecycle

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Upgrade code artifacts: Theory

Upgrade code artifacts: Theory

From the course: SharePoint Framework for Developers: 3 Deployment, Upgrades, and Lifecycle

Start my 1-month free trial

Upgrade code artifacts: Theory

“

- [Instructor] Deploying SharePoint framework solution artifacts that rely on code, JavaScript files, things that go on the CDN require a very special workflow and consideration. Version one is easy. You write the code, you deploy stuff to the CDN, you deploy your sppkg and the wep part works. Version two is where things get a little interesting. You update your code and you build your application again. At that point you don't deploy the sppkg. You first deploy your files to the CDN. Why? Well this is because you don't want the new files to become available until the user chooses to upgrade. So you deploy things to the CDN first. Don't deploy the sppkg. The old web part shows still. Now, you deploy the new sppkg and end users can now pull the new web part in their site collections and, therefore, it'll start pulling the new files and that is how version one upgrades to version two. So, again, upgrading your solution. Always upgrade the SPFx solution package. This contains the updated…

Contents