Showing results for 
Search instead for 
Did you mean: 
New Member

error MSB4057: The target "GetProjectOutputPath" does not exist i n the project.

I am getting this error in the last step of creating the solution package while executing the command 'msbuild'

after the step msbuild /t:restore


I have taken an existing code from PCF gallery and trying to use the same.


Attached is the screenshot of error 


"C:\Folder\DataSet\Solution\Solution.cdsproj" (default target) (1) ->
(ResolveAssemblyReferences target) ->
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\bin\Microsoft.Common.CurrentVersion.targe
ts(2110,5): warning MSB3245: Could not resolve this reference. Expected a file but got directory "C:\Folder\DataSet\Con
trol\out\controls\". If this reference is required by your code, you may get compilation errors. [C:\Folder\DataSet\Sol

"C:\Folder\DataSet\Solution\Solution.cdsproj" (default target) (1) ->
"C:\Folder\DataSet\Control\PCF-DataSetDemo.pcfproj" (GetProjectOutputPath target) (2:4) ->
C:\Folder\DataSet\Control\PCF-DataSetDemo.pcfproj : error MSB4057: The target "GetProjectOutputPath" does not exist i
n the project.

1 Warning(s)
1 Error(s)



Can you try a restore on pcfproj?
1. Go to directory containing pcfproj.
2. msbuild /t:restore
3. Copy restore msbuild logs.
4. Go to directory contaning cdsproj & run msbuild.
5. If this failed again, paste logs from step 3 & step 4 on this post, for us to take a detailed look.

I am suspecting you have an older version of pcf msbuild package ( targets/props) but we can confirm with the logs.
Power Apps
Power Apps

hi @Sureshkala , were you able to resolve this ? If not can you please share the details as per instructions from @devendramsft above ?


Changing the configuration to this line has resolved the issue

PackageReference Include="Microsoft.PowerApps.MSBuild.Solution" Version="0.*"


before resolving it was like

PackageReference Include="Microsoft.PowerApps.MSBuild.Solution" Version="0.1.*"

Hi Hemath,


Yes I was able to resolve this. Thanks for your follow up.



This seems like the right mitigation. Apparently, you have controls project (pcfproj) created from an older verison of CLI where we had 0.1* in our templates. cdsproj would have been created from a later version of CLI where we corrected it to 0.* in our templates. Now, cdsproj was getting build tools of version 0.3.* where pcfproj was still stuck at 0.1.*. 


We would add this to our doucmentation in trouble shooting steps & document breaking changes in build tools more descriptively. 

Helpful resources

UG GA Amplification 768x460.png

Launching new user group features

Learn how to create your own user groups today!

Power Apps Community Call Jan. 2022 768x460.png

Power Apps Community Call

Please join us on Wednesday, January 19th, at 8a PDT. Come and learn from our amazing speakers!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

Users online (887)