Live publish

Author: buck1ey

powerapps-docs/developer/common-data-service/authenticate-dot-net-framework.md

@@ -2,7 +2,7 @@
 title: "Authentication with .NET Framework applications (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "How .NET Framework applications can authenticate with Common Data Service" # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 01/25/2019
+ms.date: 05/11/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -48,6 +48,7 @@ More information: [Build Windows client applications using the XRM tools](xrm-to
 Use .NET Framework version 4.6.2 or higher when you create client applications. Only applications using Transport Level Security (TLS) 1.2 or better security can connect. TLS 1.2 is not the default protocol used by .NET Framework 4.5.2, but it is in .NET Framework 4.6.2.
 
 > [!NOTE]
+> The SDK APIs available in the [Microsoft.CrmSdk.XrmTooling.CoreAssembly](https://www.nuget.org/packages/Microsoft.CrmSdk.XrmTooling.CoreAssembly/) and other "CrmSdk" NuGet packages do not support .NET Core code development. Revised packages (containing refactored APIs) that do support .NET Core development can be found here: [Microsoft.Powerplatform.Cds.Client](https://www.nuget.org/packages/Microsoft.Powerplatform.Cds.Client/) and [Microsoft.Dynamics.Sdk.Messages](https://www.nuget.org/packages/Microsoft.Dynamics.Sdk.Messages/).<p/>
 > **Known Issue with Visual Studio 2015**
 > 
 > When you are running your project/solution in VS 2015 in debug mode, you may not be able to connect. This happens regardless of whether you are using a Target Framework of 4.6.2 or higher. This can occur because the Visual Studio hosting process is compiled against .NET 4.5 which means by default it does not support TLS 1.2. You can disable the Visual Studio hosting process as a work around. 

powerapps-docs/developer/common-data-service/use-multi-tenant-server-server-authentication.md

@@ -62,12 +62,12 @@ In this scenario any Common Data Service tenant can potentially use your multi-t
  You will create a multi-tenant web application or service which uses Azure AD as the authentication provider.  
 
  Exactly how you do this will not be the focus of this topic. There are a number of ways you can approach this and make choices that fit your requirements or preferences. See the following links for more information and samples:  
+
+- [Build a multi-tenant SaaS web application using Azure AD & OpenID Connect](https://github.com/Azure-Samples/active-directory-dotnet-webapp-multitenant-openidconnect)
 
-- [Build a multi-tenant SaaS web application using Azure AD & OpenID Connect](https://azure.microsoft.com/documentation/samples/active-directory-dotnet-webapp-multitenant-openidconnect/)  
-  
-- [Build a multi-tenant SaaS web application that calls a web API using Azure AD](https://azure.microsoft.com/documentation/samples/active-directory-webapp-webapi-multitenant-openidconnect-aspnetcore/)  
+- [An ASP.NET Core Web app signing-in users in any org with the Microsoft identity platform](https://github.com/Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2/tree/master/1-WebApp-OIDC/1-2-AnyOrg)  
 
-  Azure AD requires the following values to register your application:  
+Azure AD requires the following values to register your application:  
 
 |Value|Description|  
 |-----------|-----------------|  

powerapps-docs/developer/component-framework/add-custom-controls-to-a-field-or-entity.md

@@ -14,7 +14,7 @@ ms.topic: "article"
 
 # Add code components to a field or entity in model-driven apps
 
-Code components let you transform fields that traditionally contain text into visualizations. Similarly, you can use code components to transform datasets, such as a view, to display in a more visual rendering rather than a list of records. code components can appear as visualizations on forms, dashboards, views, and homepage grids. 
+Code components let you transform fields that traditionally contain text into visualizations. Similarly, you can use code components to transform datasets, such as a view, to display in a more visual rendering rather than a list of records. Code components can appear as visualizations on forms, dashboards, views, and homepage grids. 
 
 
    > [!div class="mx-imgBorder"] 
@@ -93,4 +93,4 @@ To add a code component like data-set component or simple table component to a g
 
 [Implementing components in TypeScript](implementing-controls-using-typescript.md)<br/>
 [Power Apps component framework API reference](reference/index.md)<br/>
-[Power Apps component framework overview](overview.md)
+[Power Apps component framework overview](overview.md)

powerapps-docs/developer/component-framework/create-custom-controls-using-pcf.md

@@ -19,9 +19,9 @@ This article demonstrates how to create and deploy code components using Power A
 
 ## Create a new component
 
-To begin, open **Developer Command Prompt for VS 2017** after installing Power Apps CLI.
+To begin, open **Developer Command Prompt for VS 2017 or higher** after installing Power Apps CLI.
 
-1. In the Developer Command Prompt for VS 2017, create a new folder on your local machine, for example, *C:\Users\your name\Documents\My_code_Component* using the command `mkdir <Specify the folder name>`.
+1. In the Developer Command Prompt, create a new folder on your local machine, for example, *C:\Users\your name\Documents\My_code_Component* using the command `mkdir <Specify the folder name>`.
 2. Go to the newly created folder using the command `cd <specify your new folder path>`.
 3. Create a new component project by passing some basic parameters using the command:
 

powerapps-docs/developer/component-framework/implementing-controls-using-typescript.md

@@ -29,7 +29,7 @@ The following steps are required to build a linear slider code component:
 
 To create a new project:
 
-1. Open a **Developer Command Prompt for VS 2017** window. Create a new folder for the project using the following command: 
+1. Open a **Developer Command Prompt for VS 2017 or higher** window. Create a new folder for the project using the following command: 
     ```CLI
      mkdir LinearComponent
     ```
@@ -374,7 +374,7 @@ Follow these steps to create and import a [solution](https://docs.microsoft.com/
     > [!NOTE]
     > Make sure that **NuGet targets & Build Tasks** is checked. To enable it:
     > - Open **Visual Studio Installer**.
-    > - For Visual Studio 2017, select **Modify**.
+    > - For Visual Studio 2017 or higher, select **Modify**.
     > - Select **Individual Components**.
     > - Under **Code Tools**, check **NuGet targets & Build Tasks**.
 

powerapps-docs/developer/component-framework/issues-and-workarounds.md

@@ -25,7 +25,7 @@ Here are some common issues that you might come across while using the Power App
 **Workaround**:
 
 - Open Visual Studio Installer.
-- For Visual Studio 2017, select **Modify**.
+- For Visual Studio 2017 or higher, select **Modify**.
 - Select **Individual Components**.
 - Under Code Tools, check **NuGet targets & Build Tasks**.
 

powerapps-docs/developer/component-framework/use-sample-components.md

@@ -14,23 +14,27 @@ ms.topic: "article"
 
 # How to use the sample components?
 
-All the sample components listed under this section are available to download from [here](https://go.microsoft.com/fwlink/?linkid=2088525) so that you can try them out in your model-driven or canvas apps.
+All the sample components listed under this section are available to download from [here](https://github.com/microsoft/PowerApps-Samples/tree/master/component-framework) so that you can try them out in your model-driven or canvas apps.
 
-The individual sample component topics under this section provide you an overview of the sample component, it's visual appearance, and the manifest, code, and resources for the sample component.
+The individual sample component topics under this section provide you an overview of the sample component, it's visual appearance, manifest, code, and resources for the sample component.
 
 ## Before you can try the sample components
 
 To try the sample components, you must first:
 
-- [Download](https://go.microsoft.com/fwlink/?linkid=2088525) the sample components so that you have a local copy.
+- [Download](https://github.com/microsoft/PowerApps-Samples/tree/master/component-framework) the sample components so that you have a local copy.
 - Install [Power Apps CLI](https://aka.ms/PowerAppsCLI).
 
 ## Try the sample components
 
 Follow the steps below to import and try the sample components in your model-driven or canvas app:
 
 1. Navigate to the folder on your computer where you have downloaded the sample components, and extract the .zip file.  
-1. Open Developer Command Prompt for Visual Studio 2017 and navigate to the sample component folder in the extracted folder that you want to see it in runtime. For example, navigate to the `/extracted_folder/TS_IncrementComponent` folder.
+1. Open Developer Command Prompt for Visual Studio 2017 or higher and navigate to the sample component folder in the extracted folder that you want to see it in runtime. For example, navigate to the `/extracted_folder/TS_IncrementComponent` folder.
+
+   >[!NOTE]
+   > You need to go into the specific component folder if you wish to see that particular component in runtime. You can add multiple components into a single solution file during the build process.
+
 1. Run the following command to get all the required dependencies:
     ```CLI
     npm install

powerapps-docs/developer/model-driven-apps/clientapi/reference/grids/gridcontrol/getFetchXml.md

@@ -26,7 +26,7 @@ Read-only and editable grids
 
 ## Syntax
 
-`var result = gridContext.getfetchXml();`
+`var result = gridContext.getFetchXml();`
 
 ## Return Value
 

powerapps-docs/maker/common-data-service/import-update-export-solutions.md

@@ -2,7 +2,7 @@
 title: "Import solutions | MicrosoftDocs"
 description: "Learn how to import a solution in Power Apps"
 ms.custom: ""
-ms.date: 01/30/2020
+ms.date: 05/11/2020
 ms.reviewer: ""
 ms.service: powerapps
 ms.suite: ""
@@ -26,7 +26,10 @@ search.app:
 # Import solutions 
 
  You can import solutions manually using the steps below. Only import solutions that you've obtained from a trusted source. Customizations might include code that can send data to external sources.   
-  
+ 
+> [!NOTE]
+> The system administrator security role is required to import a solution that includes a plug-in assembly. 
+ 
 1.  Sign into [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc) and select **Solutions** from the left navigation.  
 
 2.  On the command bar, select **Import**.