Skip to content

Commit e1efb95

Browse files
authored
Update code-components-alm.md
about pac pcf push --solution-unique-name parameter
1 parent 0e1cb5e commit e1efb95

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

powerapps-docs/developer/component-framework/code-components-alm.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ When developing code components, you would follow the steps below:
3838

3939
When your code component is ready for testing inside a model-driven app, canvas app, or portal, there are two ways to deploy a code component to Dataverse:
4040

41-
1. [pac pcf push](/power-platform/developer/cli/reference/pcf#pac-pcf-push): This deploys a single code component at a time to a temporary **PowerAppsTools** solution.
41+
1. [pac pcf push](/power-platform/developer/cli/reference/pcf#pac-pcf-push): This deploys a single code component at a time to a solution specified by the `--solution-unique-name` parameter, or a temporary **PowerAppsTools** solution when no solution is specified.
4242

4343
2. Using [pac solution init](/power-platform/developer/cli/reference/solution#pac-solution-init) and `msbuild` to build a `cdsproj` solution project that has references to one or more code components. Each code component is added to the `cdsproj` using [pac solution add-reference](/power-platform/developer/cli/reference/solution#pac-solution-add-reference). A solution project can contain references to multiple code components, whereas code component projects may only contain a single code component.
4444

0 commit comments

Comments
 (0)