More changes

Author: KumarVivek

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

@@ -1,5 +1,5 @@
 ---
-title: Create and deploy a custom component| Microsoft Docs
+title: Create and build a custom component| Microsoft Docs
 description: Start creating a component using the PowerApps component framework Tooling
 keywords: PowerApps component framework, Custom components, Component Framework
 ms.author: nabuthuk
@@ -12,7 +12,7 @@ ms.topic: "article"
 ms.assetid: d2cbf58a-9112-45c2-b823-2c07a310714c
 ---
 
-# Create and deploy a custom component
+# Create and build a custom component
 
 [!INCLUDE[cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
 
@@ -43,56 +43,6 @@ To build your component you can open the folder in Visual Studio Code and use th
 > [!TIP]
 > To debug your component during or after the build operation, see [Debug custom components](debugging-custom-controls.md).
 
-## Deploy your component
-
-Once you have built your component, you must deploy it to be used.  
-
-Follow the steps below to create and import a [solution](/powerapps/maker/common-data-service/solutions-overview) file:
-
-1. Create a new directory and go to it: 
-
-    `cd <new directory name>`
-1. Create a new solution project in the directory of your choice by using the command:
-
-     `pac solution init --publisherName <enter your publisher name> --customizationPrefix <enter your publisher name>` after `cd <your new folder>`.
-
-   > [!NOTE]
-   > The [publisherName](https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/reference/entities/publisher) and [cutomizationPrefix](https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/change-solution-publisher-prefix) values must be unique to your environment.
- 
-3. Once the new solution project is created, you need to refer to the ___location where the created component is located. You can add the reference by using the following command:
-
-    `pac solution add-reference --path <path or relative path of your PowerApps component framework project on disk>`
-
-4. 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 following command:
-
-    `msbuild /t:restore` then `msbuild`
-
-    > [!NOTE]
-    > - If msbuild 15 is not in the path, open Developer Command Prompt for VS 2017 to run the `msbuild` commands.
-    > - 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.
-    
-   If you would like your project build to emit a managed solution or both managed and unmanaged, open the folder where you created your solution project, edit the `cdsproj` file and uncomment the below property group:
-   ```XML
-   <PropertyGroup>
-       <SolutionPackageType>Managed</SolutionPackageType>
-    </PropertyGroup>
-    ```
-
-    You can also enable additional solution packaging [capabilities](/powerapps/developer/common-data-service/compress-extract-solution-file-solutionpackager) by adding any of the property group elements below:
-
-    ```XML
-       <PropertyGroup>
-         <SolutionPackageErrorLevel />
-         <SolutionPackageEnableLocalization />
-        <SolutionPackagerWorkingDirectory />
-        <SolutionPackageLogFilePath />
-        <SolutionPackageZipFilePath />
-        <SolutionPackageMapFilePath />
-       </PropertyGroup>
-    ```
-
-5. The generated solution zip file is located in `\bin\debug\`. You must manually [import the solution](https://docs.microsoft.com/en-us/dynamics365/customer-engagement/customize/import-update-export-solutions) using the web portal once the zip file is ready.
-
 ## Known Configuration issues and Workarounds
 
 **Msbuild error MSB4036:**
@@ -110,8 +60,9 @@ Follow the steps below to create and import a [solution](/powerapps/maker/common
 
 ### See also
 
-[Debug custom components](debugging-custom-controls.md)
-[Implementing components in TypeScript](implementing-controls-using-typescript.md)<br/>
-[Updating existing components into new tools format](updating-existing-controls.md)<br/>
+[Debug custom components](debugging-custom-controls.md)<br/>
+[Package a custom component](import-custom-controls.md)<br/>
+[Add custom components to a field or entity](add-custom-controls-to-a-field-or-entity)<br/>
+[Updating existing custom components](updating-existing-controls.md)<br/>
 [PowerApps component framework API Reference](reference/index.md)<br/>
 [PowerApps component framework Overview](overview.md)

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

@@ -12,7 +12,7 @@
       href: implementing-controls-using-typescript.md
   - name: How-to
     items:
-    - name: Create and deploy a custom component 
+    - name: Create and build a custom component 
       href: create-custom-controls-using-pcf.md
     - name: Debug a custom component
       href: debugging-custom-controls.md