-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Introduce a 'PackPrivate' mechanism for private project reference packing #47066
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
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! |
@dsplaisted I'm afraid there is some misunderstanding. This may be a cross cutting feature but it certainly isn't just a nuget limitation. After all, if I'm not mistaken the project system is not owned by the nuget team. The fact the sdk removes transitive flow of projects based on PrivateAssets has nothing to do with nuget. |
@baronfel could I ask you to take a look at this? I'm more than happy to further explain the ask if there are any questions. |
This issue is related to #17775. But I think this one is more generic. |
Context:
NuGet/Home#3891
What I ideally want to see is a mechanism that:
As I understand it PrivateAssets is overloaded and combines local reference semantics with packaging behaviors, this is problematic. Additionally, due to the complexity of the restore phase (assets.json etc) it seems impossible to create these kinds of PackPrivate features outside of the sdk while achieving good integration. I just don't believe the hooks are there to do so.
Related:
The text was updated successfully, but these errors were encountered: