cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Sureshkala
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
ution\Solution.cdsproj]


"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)

"

5 REPLIES 5
devendramsft
Microsoft
Microsoft

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.
HemantG
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 ?

hemant 

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.

Yes. 

 

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

Announcements
PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MBAS Attendee Badge

Claim Your Badge & Digital Swag!

Check out how to claim yours today!

secondImage

Are Your Ready?

Test your skills now with the Cloud Skill Challenge.

secondImage

Demo Extravaganza is Back!

We are excited to announce that Demo Extravaganza for 2021 has started!

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

Users online (70,384)