cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
PowerApps Staff sgpchenchang
PowerApps Staff

Re: Updated PCF Tooling version is now available (August 2019)!

Hi @cakhaing ,

In addition to what @devendramsft  suggests, can you also try to located the following log file? .\WhereYouInstallPac\pac\CLI\logs\pac-log.txt

 

If so can you please attach the log? Thanks!

cakhaing
Level: Powered On

Re: Updated PCF Tooling version is now available (August 2019)!

pac-log.txt

 

2019-09-06 00:18:30.3374|INFO|bolt.cli.Worker|StartExecutingVerb
2019-09-06 00:18:30.3846|INFO|bolt.cli.Worker|Verbs: ["pcf","push"]
2019-09-06 00:18:30.3846|INFO|bolt.cli.Worker|ProductVersion: 0.4.3
2019-09-06 00:18:30.5704|INFO|bolt.module.auth.profiles.AuthProfilesManager|GetCurrent(): For Kind 'CDS'.
2019-09-06 00:18:30.7085|INFO|bolt.module.auth.store.AuthTokenStore|AcquireTokenSilentAsync(): Acquiring token for https://dynamicscode.crm6.dynamics.com
2019-09-06 00:18:32.9663|INFO|bolt.module.auth.store.AuthTokenStore|AcquireTokenSilentAsync(): Successfully acquired a token
2019-09-06 00:18:34.3419|INFO|bolt.module.cds.client.CdsClient|Connected to CDS Org
2019-09-06 00:18:34.3419|INFO|bolt.cli.Verb|Executing solution init --pn PowerAppsToolsPublisher_dyco --pp dyco.
2019-09-06 00:18:34.8762|INFO|bolt.cli.Worker|StartExecutingVerb
2019-09-06 00:18:34.9072|INFO|bolt.cli.Worker|Verbs: ["solution","init"]
2019-09-06 00:18:34.9072|INFO|bolt.cli.Worker|ProductVersion: 0.4.3
2019-09-06 00:18:34.9605|INFO|bolt.cli.Verb|CDS solution project with name 'PowerAppsTools_dyco' created successfully in current directory.
2019-09-06 00:18:34.9765|INFO|bolt.cli.Verb|CDS solution files were successfully created for this project in the sub-directory Other, using solution name PowerAppsTools_dyco, publisher name PowerAppsToolsPublisher_dyco, and customization prefix dyco.
2019-09-06 00:18:34.9765|INFO|bolt.cli.Verb|Please verify the publisher information and solution name found in the Solution.xml file.
2019-09-06 00:18:34.9919|INFO|bolt.cli.Worker|EndExecutingVerb
2019-09-06 00:18:34.9919|INFO|bolt.cli.Worker|Success: True
2019-09-06 00:18:35.0078|INFO|bolt.cli.Worker|Execution Time(ms): 60
2019-09-06 00:18:35.2303|INFO|bolt.cli.Verb|Executing solution add-reference --path C:\Tools\CustomControl\PCF-ReactDemo.
2019-09-06 00:18:35.7521|INFO|bolt.cli.Worker|StartExecutingVerb
2019-09-06 00:18:35.7830|INFO|bolt.cli.Worker|Verbs: ["solution","add-reference"]
2019-09-06 00:18:35.7997|INFO|bolt.cli.Worker|ProductVersion: 0.4.3
2019-09-06 00:18:35.8368|INFO|bolt.cli.Verb|Project reference successfully added to CDS solution project.
2019-09-06 00:18:35.8534|INFO|bolt.cli.Worker|EndExecutingVerb
2019-09-06 00:18:35.8534|INFO|bolt.cli.Worker|Success: True
2019-09-06 00:18:35.8534|INFO|bolt.cli.Worker|Execution Time(ms): 41
2019-09-06 00:18:35.9691|INFO|bolt.cli.Verb|Temporary solution wrapper created at C:\Tools\CustomControl\PCF-ReactDemo\obj\PowerAppsTools_dyco
2019-09-06 00:18:35.9837|INFO|bolt.cli.Verb|File dotnet.exe not found.; looking for msbuild.exe
2019-09-06 00:18:35.9837|INFO|bolt.cli.Verb|Found msbuild.exe C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin\MSBuild.exe; building solution using msbuild.exe.

 

Here is my screen recording. https://www.youtube.com/watch?v=4ylvho7jI_k

Please skip from 2:00 to 2:40 where I restarted my VM.

 

Can you please check whether you have v4.0 folder under C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework. If you have it, can you please rename it to something else and re-run 'pac pcf push' command?

 

If it is still working, can you please check line 57 in C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets whether it is referencing to v4.6.2?

 

In my case, I temporarily solve the issue either

1. by cloning v4.6.2 folder under C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework to v4.0

OR

2. by changing TargerFrameworkVersion from v4.0 to v4.6.2 in C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets

 

As you can see in my screen recording, I can successfully build using 'msbuild' only with .net v4.6.2.

Shouldn't 'pac pcf push' work with v4.6.2 as well?

sheldoncopper73
Level: Powered On

Re: Updated PCF Tooling version is now available (August 2019)!

Love the push feature great time saver and been using since a week, only issue(feedback)  I am facing is that after one solution push I have wait few minutes for next push, It gives error :

"The process cannot access the file '.path\obj\PowerAppsTools_ikl' because it is being used by another process. "

PowerApps Staff sgpchenchang
PowerApps Staff

Re: Updated PCF Tooling version is now available (August 2019)!

@Sheb , We are aware of this issue and it has been fixed. Unfortunately you will have to wait until the next update which will take place at the end of September. Sorry for the inconvenience.

liun
Level: Powered On

Re: Updated PCF Tooling version is now available (August 2019)!

New issue:

I built a PCF and packaged with both solution types (managed.zip and unmanaged.zip). 

Import the unmanaged into a DEV instance, then exported as managed solution (exported_managed.zip) to get ready to import into downstream instances (QA/UAT/PRD). 

When I unpack the managed.zip and exported_managed.zip, I expect them to be similar, and both should be able to be imported into new environments. 

However that's not the case. It looks like the PCF build produced zip added publisher prefix (which is new in Aug tooling) to the component name, but the export one does not, causing import mismatch and fail. Please see the file compare between the two solution.xml. 

So will the tooling stop adding prefix, or the CRM export will add prefix in the future?

 

 

 

PowerApps Staff peterv333
PowerApps Staff

Re: Updated PCF Tooling version is now available (August 2019)!

We appologize for the issue you are experiencing! We are aware of this behavior and are working on a fix that will address the export issue. The prefix is there to ensure uniqueness of each component thus its essential that it is added.

Highlighted
liun
Level: Powered On

Re: Updated PCF Tooling version is now available (August 2019)!

@peterv333 Thanks. So we'll just use the built solution file for now, until the export process can add prefix. 

Helpful resources

Announcements
firstImage

Watch Sessions On Demand!

Continue your learning in our online communities.

SecondImage

PowerApps Monthly Community Call

Next Wednesday, September 18th at 8am PDT

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

FirstImage

Power Platform World Tour

Coming to a city near you

thirdimage

PowerApps Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

FourthImage

Join PowerApps User Group!!

Connect, share, and learn with your peers year-round

SecondImage

Power Platform Summit North America

Register by September 5 to save $200

Users Online
Currently online: 48 members 4,588 guests
Please welcome our newest community members: