-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[8.0 preview 3] NuGet package validation fails when UseArtifactsOutput=true #31882
Comments
Thanks for creating this issue! We believe this issue is related to NuGet tooling, which is maintained by the NuGet team. Thus, we closed this one and encourage you to raise this issue in the NuGet repository instead. Don’t forget to check out NuGet’s contributing guide before submitting an issue! If you believe this issue was closed out of error, please comment to let us know. Happy Coding! |
@dotnet/area-infrastructure-libraries a new issue has been filed in the ApiCompat area, please triage |
Reopening because the error is triggered from ApiCompat, not NuGet. |
@martincostello thanks for reporting. I submitted #31906 to fix the immediate PackageValidation issue. That said, there appears to be a bigger issue with UseArtifactsOutput when the TargetFramework couldn't be determined. cc @dsplaisted @rainersigwald |
The following logic is incorrect @dsplaisted: sdk/src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.DefaultOutputPaths.targets Lines 56 to 58 in c7b5cc6
A
|
Thanks for reporting this! @ericstj @ViktorHofer I think several fixes are needed here. I've submitted #31919 to fix the intermediate directory to not try to include the However, with the new output path format, the inner build intermediate and output paths are no longer subfolders of the outer build paths. So there's nothing that guarantees that the intermediate output path will be created. Normally the @zivkan I think it may be a good idea to update the pack targets as well. Currently the |
Describe the bug
If UseArtifactsOutput=true and NuGet package validation is enabled, an error occurs when running
dotnet pack
.It appears that the package validation functionality does not understand the new layout of the output, and looks in the wrong folder for the
.nupkg
file to validate.Specifically, there appears to be a dangling
_
in the name of the folder, I'm guessing because it's expecting there to be a TFM there.To Reproduce
build.ps1
Exceptions (if any)
Further technical details
The text was updated successfully, but these errors were encountered: