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?

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

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?

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.