Skip to content

Commit c2eb683

Browse files
committed
Updating TOC to match latest articles
1 parent 21c3c72 commit c2eb683

File tree

2 files changed

+62
-0
lines changed

2 files changed

+62
-0
lines changed
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
# Using Custom Dialogs with SharePoint Framework Extensions
2+
3+
Introduction
4+
5+
Dialog is also avaialble for web parts.
6+
7+
> Notice that the SharePoint Framework dialog is currently in preview status and we are looking to collect feedback before it's officially released. Please provide us feedback by using the [sp-dev-docs repository Issue list](https://github.com/SharePoint/sp-dev-docs/issues).
8+
9+
## Setup your Environment
10+
11+
Before you can complete this guide you will need to ensure you have [setup your environment](https://dev.office.com/sharepoint/docs/spfx/set-up-your-development-environment) for development
12+
using SharePoint Framework and that you are using latest SharePoint Framework Yeoman templates.
13+
14+
> You can update your SharePoint Framework Yeoman templates by running following command `npm install -g @microsoft/generator-sharepoint`.
15+
16+
## Create a New Project
17+
18+
Start by creating a new folder for the project using your console of choice:
19+
20+
```sh
21+
md dialog-cmd
22+
```
23+
24+
And enter that folder
25+
26+
```sh
27+
cd dialog-cmd
28+
```
29+
30+
The run the Yeoman generator for SharePoint Framework
31+
32+
```sh
33+
yo @microsoft/sharepoint
34+
```
35+
36+
When prompted:
37+
38+
* Accept the default value of **dialog-cmd** as your solution name and press **Enter**.
39+
* Choose **Extension (Preview)** as the client-side component type to be created.
40+
* Choose **ListView Command Set (Preview)** as the extension type to be created.
41+
42+
The next set of prompts will ask for specific information about your extension:
43+
44+
* Accept the default value of **DialogDemo** as your extension name and press **Enter**.
45+
* Accept the default value of **DialogDemo description** as your extension description and press **Enter**.
46+
47+
![Yeoman SharePoint generator prompts to create an extension solution](../../../../images/ext-com-yeoman-prompts.png)
48+
49+
At this point, Yeoman will install the required dependencies and scaffold the solution files along with the **HelloWorld** extension. This might take a few minutes.
50+
51+
When the scaffold is complete, you should see the following message indicating a successful scaffold:
52+
53+
![SharePoint client-side solution scaffolded successfully](../../../../images/ext-com-yeoman-complete.png)
54+
55+
For information about troubleshooting any errors, see [Known issues](../basics/known-issues).
56+
57+
Once the solution scaffolding is completed, type the following into the console to start Visual Studio Code.
58+
59+
```
60+
code .

misc/SharePointDocumentationToc.xml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,8 @@
6161
<Item text="Share data between web parts" url="spfx/web-parts/guidance/share-data-between-web-parts" SEODescription="Options and practices on sharing data cross multiple web parts in single page." />
6262
<Item text="Sharing data between web parts (tutorial)" url="spfx/web-parts/guidance/tutorial-share-data-between-web-parts-global-variable" SEODescription="Share data between web parts using a global variable (tutorial)." />
6363
<Item text="Migrating Script Editor Web Part customizations" url="spfx/web-parts/guidance/migrate-script-editor-web-part-customizations" SEODescription="Migrate existing Script Editor Web Part customizations to the SharePoint Framework." />
64+
<Item text="Migrating jQuery and DataTables solution" url="spfx/web-parts/guidance/migrate-jquery-datatables-script-to-spfx" SEODescription="Migrate jQuery and DataTables solution built using Script Editor Web Part to SharePoint Framework." />
65+
<Item text="Migrating jQuery and FullCalendar solution" url="spfx/web-parts/migrate-jquery-fullcalendar-script-to-spfx" SEODescription="Migrate jQuery and FullCalendar solution built using Script Editor Web Part to SharePoint Framework." />
6466
<Item text="Connect to API secured with Azure Active Directory" url="spfx/web-parts/guidance/connect-to-api-secured-with-aad" SEODescription="Call securely APIs from client-side web parts, which are secured using Azure Active Directory." />
6567
<Item text="Office UI Fabric integration" url="spfx/web-parts/guidance/office-ui-fabric-integration" SEODescription="Using Office UI Fabric Core and Fabric React in SPFx client-side web parts." />
6668
<Item text="Build web parts with SP PnP JS" url="spfx/web-parts/guidance/use-sp-pnp-js-with-spfx-web-parts" SEODescription="Using SharePoint PnP JS library in your SharePoint Framework client-side web part implementation." />

0 commit comments

Comments
 (0)