The updated version of PCF tooling (PowerApps CLI) is now available! Today we released new capabilities for several of our most popular feature requests in the PowerApps CLI. We are now providing PowerApps component framework developers the ability to not only see changes in the test harness as they are made but to also push components directly into an org using the CLI. These innovations will greatly speed up the development inner loop!
The push capability will make you more efficient because it bypasses the custom component versioning requirements and does not require you to build your solution in order to import into your development environment. The watch capability removes the need to reload your test harness after every change is made.
If you have not yet updated your PowerApps CLI to the latest version, this release is definitely the time to do it! To get all the latest capabilities, please install the latest MSI by following the tooling documentation .
Once you have the latest version of the CLI you can always refer to the tooling documentation or get quickly started using the steps outlined below.
The test harness can be set up to watch and recompile the source code of your PowerApps Component Framework projects. To enable watch mode, start the test harness using the command “npm start watch” from the command prompt. The watch capability will detect changes in index.ts, ControlManifest.Input.xml, other bundled .ts files, and all resources declared in the manifest, then rebuild your component and automatically update the test harness without having to restart it.
To start pushing your custom component directly into an environment, there is a quick but essential step of setting up your authentication profile in the CLI. This setup is a one-time effort where your profile can be saved for future connections. Here is how to do it:
To start with, please create your authentication profile using the command:
"pac auth create --url"
Now that you have an authentication profile, you can start pushing your updated component by following two simple steps:
1. In your VS command prompt, go to the root directory of your custom component project
2. Run the command "pac pcf push --publisher-prefix"
We hope you enjoy the newly added features and are excited to hear what you thinks about them. If you have questions or other feedback, please let us know on the PowerApps component framework forum. We look forward to hearing from you!
The watch was already possible if you altered the pcf-scripts a bit. Love the new push feature!
When I test 'pac pcf push', I am getting the following error. My machine was installed with .NET 4.6.2
It seems the command requires .NET 4.0. Does it mean I have to install both .NET 4.6.2 and .NET 4.0? Otherwise, can you please override Framework path in executing msbuild command?
[23:1:59] [clean] Initializing...
[23:1:59] [clean] Cleaning build outputs...
[23:1:59] [clean] Succeeded
Cleaning output directory: bin\Debug\, Intermediate directory: obj\Debug\ and Solution Packager working directory: obj\Debug\
Removing log file: bin\Debug\SolutionPackager.log and generated solution package: bin\Debug\PowerAppsTools_dyco.zip
C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(1183,5): error MSB3644: The reference assemblies for framework ".NETFramework,Version=v4.0" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend.
Hi cakhaing,
Where did you see these outputs? The snippet you pasted above was not something one would observe on command prompt during pcf push. Can you provide my specifics of repros? Thanks!
I can run "msbuild" under the path where .cdsproj is located.
The followings are from build.log
Restore completed in 14.83 ms for C:\Tools\CustomControl\PCF-ReactDemo\PCF-ReactDemo.pcfproj.
Restore completed in 402.42 ms for C:\Tools\CustomControl\PCF-ReactDemo\obj\PowerAppsTools_dyco\PowerAppsTools_dyco.cdsproj.
> pcf-project@1.0.0 clean C:\Tools\CustomControl\PCF-ReactDemo
> pcf-scripts clean "--noColor" "--buildMode" "development" "--outDir" "C:\Tools\CustomControl\PCF-ReactDemo\out\controls" "--buildSource" "MSBuild"
[14:25:17] [clean] Initializing...
[14:25:17] [clean] Cleaning build outputs...
[14:25:17] [clean] Succeeded
Cleaning output directory: bin\Debug\, Intermediate directory: obj\Debug\ and Solution Packager working directory: obj\Debug\
Removing log file: bin\Debug\SolutionPackager.log and generated solution package: bin\Debug\PowerAppsTools_dyco.zip
C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(1183,5): error MSB3644: The reference assemblies for framework ".NETFramework,Version=v4.0" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend. [C:\Tools\CustomControl\PCF-ReactDemo\PCF-ReactDemo.pcfproj]
If I correctly understand, 'pac pcf push' is to eliminate the creation of .cdsproj. Probably, it is an issue with reference path.
For example, I have following folder structure. Solution folder contains .cdsproj. If I run 'msbuild' command in Solution folder, it works.
If I run 'pac pcf push' under the parent folder, I got this error.
Output in build.log as following.
Restore completed in 14.83 ms for C:\Tools\CustomControl\PCF-ReactDemo\PCF-ReactDemo.pcfproj.
Restore completed in 402.42 ms for C:\Tools\CustomControl\PCF-ReactDemo\obj\PowerAppsTools_dyco\PowerAppsTools_dyco.cdsproj.
> pcf-project@1.0.0 clean C:\Tools\CustomControl\PCF-ReactDemo
> pcf-scripts clean "--noColor" "--buildMode" "development" "--outDir" "C:\Tools\CustomControl\PCF-ReactDemo\out\controls" "--buildSource" "MSBuild"
[14:25:17] [clean] Initializing...
[14:25:17] [clean] Cleaning build outputs...
[14:25:17] [clean] Succeeded
Cleaning output directory: bin\Debug\, Intermediate directory: obj\Debug\ and Solution Packager working directory: obj\Debug\
Removing log file: bin\Debug\SolutionPackager.log and generated solution package: bin\Debug\PowerAppsTools_dyco.zip
C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(1183,5): error MSB3644: The reference assemblies for framework ".NETFramework,Version=v4.0" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend. [C:\Tools\CustomControl\PCF-ReactDemo\PCF-ReactDemo.pcfproj]
My .NETFramework folder under Reference Assemblies looks like this. (only v4.6.2 is existed)
If I create a new folder named 'v.4.0' and copy assemblies from v4.6.2, 'pac pcf push' works.
@devendramsft wrote:
Are you running on Windows 10?
Can you please also review the pre-reqs for powerapps CLI & let us know the configuration that you have?
a) OS version
b) DotNet core version
c) VS 2017/VS 2019 /VS edition.
https://docs.microsoft.com/en-us/powerapps/developer/component-framework/get-powerapps-cli
a) Windows 10 Pro
b) .NET Framework 4.6.2
c) VS Code for development and VS Build Tools 2019 for build
I can create, and build PCF projects. Watch mode works fine, but not 'pac pcf push'.
I have posted more details at https://powerusers.microsoft.com/t5/PowerApps-component-framework/Updated-PCF-Tooling-version-is-now...
@Anonymous wrote:The watch was already possible if you altered the pcf-scripts a bit. Love the new push feature!
npm start watch provides additional capabilities in that files like ControlManifest.Input.xml as well as resource files registered in ControlManifest.Input.xml are watched.
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08 23 @WarrenBelz 31 @DBO_DV 10 @Amik 19 AmínAA 6 @mmbr1606 12 @rzuber 4 @happyume 7 @Giraldoj 3@ANB 6 (tie) @SpongYe 6 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08 10@WarrenBelz 25 @DBO_DV 6@mmbr1606 14 @AmínAA 4 @Amik 12 @royg 3 @ANB 10 @AllanDeCastro 2 @SunilPashikanti 5 @Michaelfp 2 @FLMike 5 @eduardo_izzo 2 Meekou 2 @rzuber 2 @Velegandla 2 @PowerPlatform-P 2 @Micaiah 2 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages