-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft.Build.Traversal: GetNativeManifest and FindUnderPath errors when attempting to build #34
Comments
It seems there are two unique issues here. error MSB4057: The target "GetNativeManifest" does not exist in the project.In newer version of MSBuild, the project-to-project call of I recommend that you use a newer version of .NET Core SDK in your If that's not an option, you'll need to specify an empty <Target Name="GetNativeManifest" /> The real one will override your empty one if its ever defined. error MSB4044: The "FindUnderPath" task was not given a value for the required parameter "Path"This is caused by some confusing logic in the MSBuild default targets here. It turns out that This is a bug and we'll get this fixed. I'll either disable the A workaround for now is to set <Project Sdk="Microsoft.Build.Traversal/1.0.22">
<PropertyGroup>
<OutputPath Condition=" '$(Configuration)' != '' ">bin\$(Configuration)\</OutputPath>
<OutputPath Condition=" '$(Configuration)' == '' ">bin\Debug\</OutputPath>
</PropertyGroup>
<ItemGroup>
<ProjectReference Include="src\**\*.*proj" />
</ItemGroup>
</Project> |
The fix for the "FindUnderPath" error is available in 1.0.34. Let me know if it solves that issue. |
Confirmed the Thanks for the quick help @jeffkl! It's much appreciated :) |
I'm not sure if this belongs here or MSBuild, but I'm getting the following when attempting to use Traversal as suggested in dotnet/msbuild#1730 (comment):
Environment:
I've created a branch with the repro here: https://github.com/MiniProfiler/dotnet/tree/craver/traversal
To run:
I see related issues in MSBuild here:
...but I would assume (dangerous!) those downstream issues are from traversal double-includes of projects, or possible from the tree beneath a project (some of the projects in there reference others, with most of them referencing
MiniProfiler.Shared
at the end) not being fully evaluated on what to build? Just trying to save some time with observations here...hopefully the repro above helps more than anything.The text was updated successfully, but these errors were encountered: