-
Notifications
You must be signed in to change notification settings - Fork 525
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
Support PrivateAssets in NuGet packages #2370
Comments
original by @matthid
Good catch. |
Paket should implement something similar to the privateassets spec of packagereference. |
More info (via @enricosada, thanks): https://github.com/NuGet/Home/wiki/PackageReference-Specification https://docs.microsoft.com/en-us/nuget/schema/nuspec#dependencies PrivateAsset leads to include attribute: I think this needs to be a transitive setting, but we should first check that with dotnet cli. |
Any chance for this? Currently it's effectively impossible for me package with neither The former adds development dependencies to nupkg and the latter only packages one target. Please don't force me to use csproj dependencies :) EDIT |
@matthid we already have private assets. What's still to do here? |
And how? We can close this if we add a link to the docs :) |
@forki But where does this come from? paket.references? So what (from a users standpoint) needs to be changed to make a dependency a private asset? Do we have docs around that? |
@matthid It looks like forki resolved this here: I believe it is documented here: |
Support
PrivateAssets
and dependencies who are marked asdevelopmentDependency
developmentDependency
PrivateAssets
The text was updated successfully, but these errors were encountered: