Skip to content

Commit 2db6205

Browse files
authored
Merge pull request #1694 from MicrosoftDocs/sushant-pcf-updates
Sushant PCF updates
2 parents 2a84eb8 + fb53369 commit 2db6205

File tree

2 files changed

+6
-7
lines changed

2 files changed

+6
-7
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Start creating a component using the PowerApps component framework
44
keywords: PowerApps component framework, Custom components, Component Framework
55
ms.author: nabuthuk
66
manager: kvivek
7-
ms.date: 04/23/2019
7+
ms.date: 06/20/2019
88
ms.service: "powerapps"
99
ms.suite: ""
1010
ms.tgt_pltfrm: ""
@@ -41,7 +41,7 @@ To get started, open a new Developer Command Prompt for VS 2017 after installing
4141
To build your component you can open the folder in Visual Studio Code and use the (Ctrl-Shift-B) command, then select your build options. Alternately, you can build your control quickly using `npm run build` command in your Developer Command Prompt for VS 2017 window.
4242

4343
> [!TIP]
44-
> To debug your component during or after the build operation, see [Debug custom components](debugging-custom-controls.md).
44+
> To debug your component during or after the build operation, see [Debug a custom component](debugging-custom-controls.md).
4545
4646
## Known Configuration issues and Workarounds
4747

powerapps-docs/developer/component-framework/import-custom-controls.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Process to import custom controls
44
keywords:
55
ms.author: nabuthuk
66
manager: kvivek
7-
ms.date: 04/23/2019
7+
ms.date: 06/20/2019
88
ms.service: "powerapps"
99
ms.suite: ""
1010
ms.topic: "article"
@@ -26,10 +26,9 @@ Follow the steps below to create and import a solution file:
2626
3. To generate a zip file from your solution project, you will need to `cd` into your solution project directory and build the project using the command `msbuild/t:restore` and `msbuild`
2727

2828
> [!NOTE]
29-
> If msbuild 15 is not in the path, open Developer Command Prompt for Vs 2017 to run the msbuild commands.
30-
31-
> [!NOTE]
32-
> Building the solution in the debug configuration, generates an unmanaged solution package. A managed solution package is generated by building the solution in release configuration. These settings can be overridden by specifying SolutionPackageType property in cdsproj file.
29+
> - If msbuild 15 is not in the path, open Developer Command Prompt for Vs 2017 to run the msbuild commands.
30+
> - Building the solution in the *debug* configuration generates an unmanaged solution package. A managed solution package is generated by building the solution in *release* configuration. These settings can be overridden by specifying SolutionPackageType property in cdsproj file.
31+
> - You can set the msbuild configuration to `Release` to issue a production build. Example: `msbuild /p:configuration=Release`
3332
3433
4. The generated solution files are located in `\bin\debug\`.
3534
5. You should manually import the solution using the web portal.

0 commit comments

Comments
 (0)