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

Support PrivateAssets in NuGet packages #2370

Open
2 tasks
matthid opened this issue May 26, 2017 · 9 comments
Open
2 tasks

Support PrivateAssets in NuGet packages #2370

matthid opened this issue May 26, 2017 · 9 comments

Comments

@matthid
Copy link
Member

matthid commented May 26, 2017

Support PrivateAssets and dependencies who are marked as developmentDependency

  • developmentDependency
  • PrivateAssets
@matthid matthid added the bug label May 26, 2017
@enricosada
Copy link
Collaborator

enricosada commented May 27, 2017

original by @matthid

Paket.Core depends on FSharp.NET.Sdk

It probably shouldn't, see https://www.nuget.org/packages/Paket.Core
Interestingly I think this "bug" makes it possible for all the other projects to build with msbuild 15.

We probably need a way to mark a dependency as "compile-time" only.

/cc @forki @enricosada

Good catch.
It shoudnt.
That's the privateassets=all part

@enricosada
Copy link
Collaborator

Paket should implement something similar to the privateassets spec of packagereference.
That's used for analyzes, compile time stuff (like test lib helpers) etc
And is written in the nuspec too

@matthid matthid changed the title Paket.Core depends on FSharp.NET.Sdk Support PrivateAssets in NuGet packages Jun 12, 2017
@matthid
Copy link
Member Author

matthid commented Jun 12, 2017

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:

grafik

I think this needs to be a transitive setting, but we should first check that with dotnet cli.

@tpluscode
Copy link
Contributor

tpluscode commented May 24, 2018

Any chance for this? Currently it's effectively impossible for me package with neither dotnet pack nor paket pack because of #3191.

The former adds development dependencies to nupkg and the latter only packages one target. Please don't force me to use csproj dependencies :)

EDIT
I guess I can still use type file to define entire package manually. I guess this will do for now...

@forki
Copy link
Member

forki commented May 25, 2018

@matthid we already have private assets. What's still to do here?

@matthid
Copy link
Member Author

matthid commented May 25, 2018

And how? We can close this if we add a link to the docs :)

@forki
Copy link
Member

forki commented May 25, 2018

image

@matthid
Copy link
Member Author

matthid commented May 27, 2018

@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?

@bigjonroberts
Copy link

bigjonroberts commented Jul 14, 2018

@matthid It looks like forki resolved this here:
85f3c9e
The syntax is to add copy_local:true in the paket.dependencies file.

I believe it is documented here:
https://fsprojects.github.io/Paket/dependencies-file.html#Controlling-whether-assemblies-should-be-copied-to-the-output-directory-during-build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants