Skip to content

Commit 532de69

Browse files
committed
Tweaks
1 parent f87f471 commit 532de69

File tree

4 files changed

+64
-34
lines changed

4 files changed

+64
-34
lines changed

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

Lines changed: 0 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -97,24 +97,6 @@ Follow the steps below to create and import a [solution](/powerapps/maker/common
9797

9898
To add a custom component like data-set component or simple table component to a grid or view, follow the steps mentioned in the topic [Add controls to fields and entities](add-custom-controls-to-a-field-or-entity.md).
9999

100-
## Telemetry
101-
102-
The feature team is aggregating anonymized telemetry in order to understand which features or capabilities in the PowerApps CLI tool are most often used by the developers. The aggregated data allows us to provide the best experience to the customers by focusing on what’s truly is important.
103-
104-
> [!NOTE]
105-
> To disable the telemetry collection, run the command `pac telemetry --enable false`. To turn the telemetry back, use the command `pac telemetry --enable true`.
106-
107-
## How to Uninstall Microsoft PowerApps CLI
108-
109-
To uninstall the CLI tool please run the MSI from [here](http://download.microsoft.com/download/D/B/E/DBE69906-B4DA-471C-8960-092AB955C681/powerapps-cli-0.1.51.msi). If you are Private Preview Participant and have an older version of CLI, please follow below manual steps:
110-
111-
1. To find out where PowerApps CLI is installed, open a command prompt and type `where pac`
112-
1. Delete the PowerAppsCLI folder.
113-
1. Open Environment Variables tool by running command `rundll32 sysdm.cpl,EditEnvironmentVariables` in the command prompt
114-
1. Double-click on `Path` under `User variable for...` section
115-
1. Select the row containing PowerAppsCLI path and click the Delete button on the right-hand side
116-
1. Click OK twice
117-
118100
## Known Configuration issues and Workarounds
119101

120102
**Msbuild error MSB4036:**

powerapps-docs/developer/component-framework/get-powerapps-cli.md

Lines changed: 61 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Microsoft PowerApps Command Line Interface (CLI)| Microsoft Docs
3-
description: "Get the Microsoft PowerApps Command Line Interface (CLI) to create, debug and deploy custom components using PowerApps component framework."
2+
title: Get tooling for PowerApps component framework | Microsoft Docs
3+
description: "Get the Microsoft PowerApps CLI to create, debug and deploy custom components using PowerApps component framework."
44
keywords: PowerApps component framework, Custom components, Component Framework
55
ms.author: nabuthuk
66
manager: kvivek
@@ -12,11 +12,11 @@ ms.topic: "article"
1212
ms.assetid: f393f227-7a88-4f25-9036-780b3bf14070
1313
---
1414

15-
# Get Microsoft PowerApps Command Line Interface (CLI)
15+
# Get tooling for PowerApps component framework
1616

1717
[!INCLUDE[cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
1818

19-
Use Microsoft PowerApps Command Line Interface (CLI) to create, debug and deploy custom components using PowerApps component framework. PowerApps CLI enables developers to quickly create PowerApps component framework components and will in the future be expanded to include support for additional development and Application Lifecycle Management (ALM) experiences.
19+
Use **Microsoft PowerApps CLI** (commnad-line interface) to create, debug and deploy custom components using PowerApps component framework. PowerApps CLI enables developers to quickly create PowerApps component framework components and will in the future be expanded to include support for additional development and Application Lifecycle Management (ALM) experiences.
2020

2121
## What is Microsoft PowerApps CLI?
2222

@@ -28,7 +28,7 @@ Microsoft PowerApps CLI is a simple, single-stop developer command line interfac
2828
> - If you give feedback about the software to Microsoft, you give to Microsoft, without charge, the right to use, share and commercialize your feedback in any way and for any purpose.
2929
> - Microsoft doesn't provide support for this preview feature. Microsoft Technical Support won’t be able to help you with issues or questions.
3030
31-
## Get Microsoft PowerApps CLI
31+
## Install Microsoft PowerApps CLI
3232

3333
To use Microsoft PowerApps CLI, do the following:
3434

@@ -46,6 +46,62 @@ To use Microsoft PowerApps CLI, do the following:
4646
> - To deploy your custom component using PowerApps CLI, you must have a Common Data Service environment with system administrator or system customizer privileges.
4747
> - Currently, PowerApps CLI is supported only on Windows 10.
4848
49+
## Update Microsoft PowerApps CLI to the latest version
50+
51+
To update your Microsoft PowerApps CLI to the latest version 02.856.1 and take advantage of all the latest capabilities, run the following command in the Developer Command Prompt for VS 2017:
52+
53+
```CLI
54+
pac install latest
55+
```
56+
57+
### What else do I need to know?
58+
59+
If you have already created a solution project or PowerApps component framework project, ensure to update these projects to the latest packages. This will help you leverage newly added capabilities with your existing projects. Newly created projects will already contain these settings.
60+
61+
- Update the version tag in your `pcfproj` located within your PowerApps component framework project folder:
62+
63+
```XML
64+
<PackageReference Include="Microsoft.PowerApps.MSBuild.Pcf" Version="0.*"/>
65+
```
66+
- Update the version tag in your `cdsproj` located within your solution project folder:
67+
68+
```XML
69+
<PackageReference Include="Microsoft.PowerApps.MSBuild.Solution" Version="0.*"/>
70+
```
71+
72+
> [!NOTE]
73+
> After making the above changes, run the command `msbuild /t:restore` to update your project to the correct version.
74+
75+
76+
- Update the version tag in your `package.json` file located within your PowerApps component framework project folder:
77+
78+
```JSON
79+
"devDependencies":{
80+
"pcf-scripts": "^0",
81+
"pcf-start": "^0"
82+
}
83+
```
84+
> [!NOTE]
85+
> After making above changes, using 'npm update' in the command prompt will always update your project to the correct version.
86+
87+
## Microsoft PowerApps CLI telemetry
88+
89+
The feature team is aggregating anonymized telemetry in order to understand which features or capabilities in the PowerApps CLI tool are most often used by the developers. The aggregated data allows us to provide the best experience to the customers by focusing on what’s truly is important.
90+
91+
> [!NOTE]
92+
> To disable the telemetry collection, run the command `pac telemetry --enable false`. To turn the telemetry back, use the command `pac telemetry --enable true`.
93+
94+
## Uninstall Microsoft PowerApps CLI
95+
96+
To uninstall the CLI tool please run the MSI from [here](http://download.microsoft.com/download/D/B/E/DBE69906-B4DA-471C-8960-092AB955C681/powerapps-cli-0.1.51.msi). If you are Private Preview Participant and have an older version of CLI, please follow below manual steps:
97+
98+
1. To find out where PowerApps CLI is installed, open a command prompt and type `where pac`
99+
1. Delete the PowerAppsCLI folder.
100+
1. Open Environment Variables tool by running command `rundll32 sysdm.cpl,EditEnvironmentVariables` in the command prompt
101+
1. Double-click on `Path` under `User variable for...` section
102+
1. Select the row containing PowerAppsCLI path and click the Delete button on the right-hand side
103+
1. Click **OK** twice.
104+
49105
### See also
50106

51107
[Implementing components in TypeScript](implementing-controls-using-typescript.md)<br/>

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

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.suite: ""
1010
ms.topic: "article"
1111
---
1212

13-
# Deploying controls into Common Data Service
13+
# Package a custom component
1414

1515
This topic demonstrates how to import custom controls into Common Data Service. After developing custom controls using the PowerApps CLI, next step is to import those controls, so that you can see the controls in runtime.
1616

@@ -34,13 +34,7 @@ Follow the steps below to create and import a solution file:
3434
4. The generated solution files are located in `\bin\debug\`.
3535
5. You should manually import the solution using the web portal.
3636

37-
## Telemetry
38-
39-
The feature team is aggregating anonymized telemetry in order to understand which features or capabilities in the PowerApps CLI tool are most often used by the developers. The aggregated data allows to provide the best experience to the customers by focusing on what’s truly is important.
40-
41-
To disable the telemetry collection, run the command `pac telemetry - -enabled false`. To turn the telemetry back, use the command `pac telemetry- -enabled true`.
42-
43-
## How to remove components from a solution
37+
## How to remove components from a solution
4438

4539
If you would like to remove a custom component from a solution, follow the steps below:
4640

powerapps-docs/developer/component-framework/toc.yml

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
href: overview.md
55
- name: "What are custom components?"
66
href: custom-controls-overview.md
7-
- name: Get PowerApps CLI
7+
- name: Get tooling
88
href: get-powerapps-cli.md
99
- name: Tutorial
1010
items:
@@ -20,8 +20,6 @@
2020
href: import-custom-controls.md
2121
- name: Add components to entities or fields
2222
href: add-custom-controls-to-a-field-or-entity.md
23-
- name: Update PowerApps CLI to latest version
24-
href: updating-tooling.md
2523
- name: Update existing custom components
2624
href: updating-existing-controls.md
2725
- name: Publish custom components on AppSource

0 commit comments

Comments
 (0)