Error packaging PCF Sample : Project Reference with output path 0, is not a valid PowerApps Component Type

microsoft / PowerApps-Samples

Sample code for Power Apps, including Dataverse, model-driven apps, canvas apps, Power Apps component framework, portals, and AI Builder.

https://docs.microsoft.com/powerapps

MIT License

1.53k stars 1.7k forks source link

Error packaging PCF Sample : Project Reference with output path 0, is not a valid PowerApps Component Type #105

Closed radupasol closed 4 years ago

radupasol commented 4 years ago

I'm getting an error on the last step of packaging the samples - on the 'msbuild' step I'm getting: ....\microsoft.powerapps.msbuild.solution\1.1.6\build\Microsoft.PowerApps.MSBuild. Solution.targets(98,5): error : Project Reference with output path 0, is not a valid PowerApps Component Type [...\TS_MapControl\solutions\solutions.cdsproj]

Tried on MapControl, IframeControl & ImageUploadControl, both on msbuild 15. and 16. tool chain

macthedev commented 4 years ago

I am getting the same issue.

After following the instructions here: https://github.com/microsoft/PowerApps-Samples/blob/master/component-framework/README.md

I successfully run msbuild /t:restore, and then when running msbuild again, i get 2 fails both with the same message as shown in the post above.

cyus commented 4 years ago

(EDITED). The app works on local but when packaging the solution the issue. Edityed not only for specific components. Really fishy older works. Only the difference is resx that was added. It seems to expect TS_LinearInputControl.exe to generated but was not found during the build process.

cyus commented 4 years ago

Got it! For some reason when solution folder is initialized, the [SolutionName].cdsproj default version is not 1.. Just modify that to 1. then do a msbuild /t:build /restore. This looks like its really not an issue its just for us beginning to work with PCF needs to pay attention to compared to various tutorials we will find online.

Nkrb commented 4 years ago

@cyus Thanks for the help solving the issue. Closing the issue. @radupasol Please re-open the issue, if you feel you need more information.