Skip to content
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

Make sure nugetize always sets EnablePackageValidation=false to avoid SDK attempting to validate a non-existent package #482

Closed
kzu opened this issue May 17, 2024 Discussed in #366 · 0 comments · Fixed by #483
Labels
bug Something isn't working

Comments

@kzu
Copy link
Member

kzu commented May 17, 2024

Discussed in #366

Originally posted by EricSteuart March 23, 2023
Using the following multi-target solution, running nugetize -p:configuration=Release gives the following errors. If I run it without the configuration specified or even if I specify it as Debug it runs fine. Running Release against a non-multi-target solution doesn't have the problem.

image

NugetizerTest - Multi-Target

@kzu kzu added the bug Something isn't working label May 17, 2024
kzu added a commit that referenced this issue May 17, 2024
Make sure nugetize always sets EnablePackageValidation=false to avoid SDK attempting to validate a non-existent package

Fixes #482
@kzu kzu closed this as completed in #483 May 17, 2024
kzu added a commit that referenced this issue May 17, 2024
Make sure nugetize always sets EnablePackageValidation=false to avoid SDK attempting to validate a non-existent package

Fixes #482
@devlooped devlooped locked and limited conversation to collaborators Nov 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant