You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/spfx/extensions/get-started/hosting-extension-from-office365-cdn.md
+24-11Lines changed: 24 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Host extension from Office 365 CDN (Hello World part 4)
3
3
description: Deploy your SharePoint Framework Application Customizer to be hosted from an Office 365 CDN and deploy that to SharePoint for end users.
4
-
ms.date: 08/27/2018
4
+
ms.date: 01/28/2020
5
5
ms.prod: sharepoint
6
6
localization_priority: Priority
7
7
ms.custom: scenarios:getting-started
@@ -29,31 +29,44 @@ You can also follow these steps by watching the video on the SharePoint PnP YouT
29
29
30
30
Office 365 CDN is the easiest way to host SharePoint Framework solutions directly from your tenant while still taking advantage of the Content Delivery Network (CDN) service for faster load times of your assets.
31
31
32
-
1.Download the [SharePoint Online Management Shell](https://www.microsoft.com/download/details.aspx?id=35588) to ensure that you have the latest version.
32
+
1.Ensure that you have the latest version of the SharePoint Online Management Shell by running the PowerShell in Administrator role and executing following PowerShell cmdlet to download latest version of the cmdlets from [PowerShell Gallery](https://www.powershellgallery.com/packages/Microsoft.Online.SharePoint.PowerShell).
33
33
34
-
2. Connect to your SharePoint Online tenant by using PowerShell:
34
+
> If you are using a non-Windows machine, you cannot use the SharePoint Online Management Shell. You can, however, manage these settings by using [Office 365 CLI](https://sharepoint.github.io/office365-cli/).
41
+
42
+
> [!NOTE]
43
+
> You can also install SharePoint Online Management Shell using [an installer](https://www.microsoft.com/en-us/download/details.aspx?id=35588) available from the Microsoft download center, but in general PowerShell gallery option is recommended.
44
+
45
+
1. Confirm module installation if asked in the PowerShell window
46
+
47
+
1. Connect to your SharePoint Online tenant by using PowerShell:
3. Get the current status of public CDN settings from the tenant level by executing the following commands one-by-one:
53
+
1. Get the current status of public CDN settings from the tenant level by executing the following commands one-by-one:
41
54
42
55
```powershell
43
56
Get-SPOTenantCdnEnabled -CdnType Public
44
57
Get-SPOTenantCdnOrigins -CdnType Public
45
58
Get-SPOTenantCdnPolicies -CdnType Public
46
59
```
47
60
48
-
4. Enable public CDN in the tenant:
61
+
1. Enable public CDN in the tenant:
49
62
50
63
```powershell
51
64
Set-SPOTenantCdnEnabled -CdnType Public
52
65
```
53
66
54
67
Public CDN has now been enabled in the tenant by using the default file type configuration allowed. This means that the following file type extensions are supported: CSS, EOT, GIF, ICO, JPEG, JPG, JS, MAP, PNG, SVG, TTF, and WOFF.
55
68
56
-
5. Execute the following command to get the list of CDN origins from your tenant:
69
+
1. Execute the following command to get the list of CDN origins from your tenant:
57
70
58
71
```powershell
59
72
Get-SPOTenantCdnOrigins -CdnType Public
@@ -80,7 +93,7 @@ Office 365 CDN is the easiest way to host SharePoint Framework solutions directl
80
93
...
81
94
```
82
95
83
-
2. Open **write-manifests.json** file from the **config** folder. This file should be only updated when you are using external CDN system. Ensure that the **cdnBasePath** attribute is exactly as shown below. If it has any other entry, automatic hosting with Office 365 Public CDN will not work.
96
+
1. Open **write-manifests.json** file from the **config** folder. This file should be **only** updated when you are using external CDN system. Ensure that the **cdnBasePath** attribute is exactly as shown below. If it has any other entry, automatic hosting with Office 365 Public CDN will not work.
84
97
85
98
```json
86
99
{
@@ -89,23 +102,23 @@ Office 365 CDN is the easiest way to host SharePoint Framework solutions directl
89
102
}
90
103
```
91
104
92
-
3. Execute the following tasks to bundle your solution. This executes a release build of your project. Due the configurations which were applied in the previous steps, it means that all assets are inside of the **sppkg** file and there is not other actions to be performed.
105
+
1. Execute the following tasks to bundle your solution. This executes a release build of your project. Due the configurations which were applied in the previous steps, it means that all assets are inside of the **sppkg** file and there is not other actions to be performed.
93
106
94
107
```
95
108
gulp bundle --ship
96
109
```
97
110
98
-
4. Execute the following task to package your solution. This command creates an **app-extension.sppkg** package in the **sharepoint/solution** folder.
111
+
1. Execute the following task to package your solution. This command creates an **app-extension.sppkg** package in the **sharepoint/solution** folder.
99
112
100
113
```
101
114
gulp package-solution --ship
102
115
```
103
116
104
-
6. Upload or drag-and-drop the newly created client-side solution package to the app catalog in your tenant, and then select the **Deploy** button. Notice how the ___domain definition is updated as **SharePoint Online** as your assets will be now automatically hosted with Office 365 CDN.
117
+
1. Upload or drag-and-drop the newly created client-side solution package to the app catalog in your tenant, and then select the **Deploy** button. Notice how the ___domain definition is updated as **SharePoint Online** as your assets will be now automatically hosted with Office 365 CDN.
105
118
106
119
107
120
108
-
7. Install the new version of the solution to your site, and ensure that it's working properly without your *locahost* hosting the JavaScript file. Notice that if you did NOT remove the package with localhost installation before updating it in the app catalog, your site is automatically running the updated version and placeholders are rendered from the CDN.
121
+
1. Install the new version of the solution to your site, and ensure that it's working properly without your *locahost* hosting the JavaScript file. Notice that if you did NOT remove the package with localhost installation before updating it in the app catalog, your site is automatically running the updated version and placeholders are rendered from the CDN.
109
122
110
123
Copy file name to clipboardExpand all lines: docs/spfx/set-up-your-development-environment.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ You can also follow these steps by watching this video on the SharePoint PnP You
27
27
28
28
Install [NodeJS LTS version 10](https://nodejs.org/dist/latest-v10.x/).
29
29
30
-
- If you are in Windows, you can use the msi installers ([x86](https://nodejs.org/dist/latest-v10.x/node-v10.19.0-x86.msi) or [x64](https://nodejs.org/dist/latest-v10.x/node-v10.19.0-x64.msi)) in this link for the easiest way to set up NodeJS.Typical insta
30
+
- If you are in Windows, you can use the msi installers ([x86](https://nodejs.org/dist/latest-v10.x/node-v10.19.0-x86.msi) or [x64](https://nodejs.org/dist/latest-v10.x/node-v10.19.0-x64.msi)) in this link for the easiest way to set up NodeJS (notice that these direct links evolve over time, so check the latest v10 from the above directory).
31
31
- If you have NodeJS already installed, check that you have the latest version by using `node -v`. It should return the current [LTS version](https://nodejs.org).
0 commit comments