SPFx 1.7 docs

Author: VesaJuvonen

.vs/ProjectSettings.json

@@ -0,0 +1,3 @@
+{
+  "CurrentProjectSetting": null
+}

.vs/VSWorkspaceState.json

@@ -0,0 +1,6 @@
+{
+  "ExpandedNodes": [
+    ""
+  ],
+  "PreviewInSolutionExplorer": false
+}

.vs/slnx.sqlite

@@ -1,7 +1,7 @@
 ---
 title: Build your first SharePoint Framework Extension (Hello World part 1)
 description: Create an extension project, and then code and debug your Application Customizer.
-ms.date: 08/30/2018
+ms.date: 11/8/2018
 ms.prod: sharepoint
 ---
 
@@ -43,15 +43,15 @@ You can also follow the steps in this article by watching the video on the Share
     * Accept the default **app-extension** as your solution name, and select Enter.
     * Select **SharePoint Online only (latest)**, and select Enter.
     * Select **Use the current folder**, and select Enter.
-    * Select **N** to require the extension to be installed on each site explicitly when it's being used. 
+    * Select **N** to allow solution to be deployed to all sites immediately.
+    * Select **N** on the question if solution contains unique permissions.
     * Select **Extension** as the client-side component type to be created. 
     * Select **Application Customizer** as the extension type to be created.
 
 5. The next set of prompts ask for specific information about your extension. When prompted:
 
     * Accept the default **HelloWorld** as your extension name, and select Enter.
     * Accept the default **HelloWorld description** as your extension description, and select Enter.
-    * For the next question **Do you want to allow the tenant admin the choice of being able to deploy the solution to all sites....**, ensure you select No (N) , and select Enter. If you select Yes (y), the scaffolding will not generate the Elements.xml feature deployment file.
 
     <br/>
 
@@ -117,7 +117,7 @@ You cannot use the local Workbench to test SharePoint Framework Extensions. You
 
     Notice that this file has been updated with the default settings matching your project. You can notice that there's a specific GUID mentioned under the customActions element. This is automatically updated to match your component when project was scaffold. If you will add new components or change the properties for the component, you will need to update this file for testing.
 
-2. Update pageURL to match your own tenant, which you want to use for testing. You can use any URL with modern experience. *This could be for example a welcome page of a new group associated team site, which would mean somewhat following URL:
+2. Update pageURL to match your own tenant, which you want to use for testing. You can use any URL with modern experience. *This could be for example a welcome page of a new group associated team site, which would mean somewhat following URL:*
 
     `https://sppnp.sharepoint.com/sites/yoursite/SitePages/Home.aspx`
 

.vs/sp-dev-docs/v15/.suo

@@ -1,7 +1,7 @@
 ---
 title: Build your first ListView Command Set extension
 description: Create an extension project, and then code and debug your extension by using SharePoint Framework (SPFx) Extensions.
-ms.date: 08/27/2018
+ms.date: 11/8/2018
 ms.prod: sharepoint
 ---
 
@@ -42,7 +42,8 @@ You can follow these steps by watching the video on the SharePoint PnP YouTube C
     * Accept the default value of **command-extension** as your solution name, and then select Enter.
     * Select **SharePoint Online only (latest)**, and select Enter.
     * Select **Use the current folder**, and select Enter.
-    * Select **N** to require the extension to be installed on each site explicitly when it's being used.
+    * Select **N** to allow solution to be deployed to all sites immediately.
+    * Select **N** on the question if solution contains unique permissions.
     * Select **Extension** as the client-side component type to be created. 
     * Select **ListView Command Set** as the extension type to be created.
 
@@ -346,6 +347,7 @@ Open **package-solution.json** from the **config** folder. The **package-solutio
     "id": "0abe5c73-1655-49d3-922b-7a47dd70e151",
     "version": "1.0.0.0",
     "includeClientSideAssets": true,
+    "isDomainIsolated": false,
     "features": [
       {
         "title": "Application Extension - Deployment of custom action.",

docs/spfx/dynamic-data.md

@@ -1,7 +1,7 @@
 ---
 title: Build your first Field Customizer extension
 description: Create an extension project, and then code and debug your extension by using SharePoint Framework (SPFx) Extensions.
-ms.date: 08/28/2018
+ms.date: 11/8/2018
 ms.prod: sharepoint
 ---
 
@@ -42,7 +42,8 @@ You can follow these steps by watching the video on the SharePoint PnP YouTube C
     * Accept the default value of **field-extension** as your solution name, and then select Enter.
     * Select **SharePoint Online only (latest)**, and select Enter.
     * Select **Use the current folder**, and select Enter.
-    * Select **N** to require the extension to be installed on each site explicitly when it's being used.
+    * Select **N** to allow solution to be deployed to all sites immediately.
+    * Select **N** on the question if solution contains unique permissions.
     * Select **Extension** as the client-side component type to be created. 
     * Select **Field Customizer** as the extension type to be created.
     
@@ -328,6 +329,7 @@ Notice also that by default **includeClientSideAssets** attribute is set to true
     "id": "80c04d1b-dca7-4d0a-86c0-9aedf904704f",
     "version": "1.0.0.0",
     "includeClientSideAssets": true,
+    "isDomainIsolated": false,
     "features": [
       {
         "title": "Application Extension - Deployment of custom action.",

docs/spfx/extensions/get-started/build-a-hello-world-extension.md

@@ -1,7 +1,7 @@
 ---
 title: Deploy your extension to SharePoint (Hello World part 3)
 description: Deploy your SharePoint Framework Application Customizer to SharePoint and see it working on modern SharePoint pages.
-ms.date: 08/27/2018
+ms.date: 11/8/2018
 ms.prod: sharepoint
 ---
 
@@ -135,6 +135,7 @@ Your **package-solution.json** should look somewhat following after the needed e
     "id": "98a9fe4f-175c-48c1-adee-63fb927faa70",
     "version": "1.0.0.0",
     "includeClientSideAssets": true,
+    "isDomainIsolated": false,
     "features": [
       {
         "title": "Application Extension - Deployment of custom action.",

docs/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api.md

@@ -0,0 +1,70 @@
+---
+title: Building Microsoft Teams Tabs using SharePoint Framework
+description: You can build your Microsoft Teams tabs using SharePoint Framework and utilize the tooling
+ms.date: 11/08/2018
+ms.prod: sharepoint
+---
+
+# Building Microsoft Teams Tabs using SharePoint Framework
+
+Starting with SharePoint Framework v1.7, you can build your Microsoft Team tabs using SharePoint Framework tooling and use SharePoint as a host for your solutions.
+
+There are following benefits on using SharePoint Framework as the platform for your Microsoft Teams tabs:
+
+- Development model is similar as for SharePoint Framework web parts
+- Technically any web part can be exposed as a tab in the Microsoft
+- You have difference scoping options on exposing your custom tab as a web part and tab in your tenant
+- Your tab will be executed in the context of the underlaying SharePoint site behind of the specific team. This means that you can take advantage of any SharePoint specific APIs or functionalities in your web part.
+
+> [!IMPORTANT]
+> This feature is currently in preview and is subject to change. It is not currently supported for use in production environments. Your feedback and input around this capability is welcome using the [SharePoint Dev Docs issue list](https://github.com/SharePoint/sp-dev-docs/issues).
+
+## Development process
+
+You can start developing Microsoft Teams tabs simply by using the `with beta` version of the SharePoint Framework 1.7 packages. High level steps to get started are as follows.
+
+1. Start SharePoint Framework Yeoman generator with the `plusbeta` switch, so that the created solution will use the preview packages.
+
+    ```
+        yo @microsoft/sharepoint --plusbeta
+    ```
+
+1. Create a solution with a client-side web part 
+1. Deploy web part using tenant-scoped deployment option to your SharePoint app catalog
+1. Package `manifest.json` located in the `/teams` folder in your solution as a zip file . This file was automatically configured with default settings when your solution was created
+1. Deploy your zip file (application) to the Microsoft Teams and start add a new tab in the preferred channel
+
+> [!NOTE]
+> You can also follow the detailed steps to get started from the [Building Microsoft Teams tab using SharePoint Framework](web-parts/get-started/using-web-part-as-ms-teams-tab.md) tutorial.
+
+## Deployment options
+
+There are few different options on getting the developed Microsoft Teams tab deployed. As both SharePoint and Microsoft Teams have their own app catalog, deployment requires operations on both services. Visibility of the new functionality can be controlled on the exact deployment mechanism.
+
+Following table shows the deployment options in table style matrix. Top row shows the Microsoft Teams deployment options and first column mapped SharePoint deployment options.
+
+| SharePoint/Teams deployment type | Manifest deployed to Store | Manifest deployed to Teams channel catalog |
+|-----------|------|-------------|
+| SharePoint tenant-scoped deployment | Solution available in all teams and all SharePoint sites | Solution available in specific team and all SharePoint Sites |
+| Site collection app catalog with tenant-scoped option in SharePoint site behind of the Team   | Not an option | Solution is available in the specific site collection and specific team  |
+| SharePoint site level deployment                    | Not an option | Solution is available in specific SharePoint site and in specific team |
+
+See following resources for additional details around the different options in both systems:
+
+- [Upload an app package to Microsoft Teams](https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/apps/apps-upload)
+- [Tenant-scoped solution deployment for SharePoint Framework solutions](https://docs.microsoft.com/en-us/sharepoint/dev/spfx/tenant-scoped-deployment)
+
+## Detecting if web part is in Teams context
+
+Page context in a web part has by default a reference to the Teams JavaScript SDK, so that you can easily get access on the Teams context when your web part is rendered as a tab.
+
+```javascript
+    this.context.microsoftTeams
+```
+
+> [!NOTE]
+> See more information around th Microsoft Teams tab context from the [Microsoft Teams development documentation](https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/tabs/tabs-context?view=msteams-client-js-latest).
+
+## See also
+
+- [Building Microsoft Teams tab using SharePoint Framework - Tutorial](web-parts/get-started/using-web-part-as-ms-teams-tab.md)