Publish .net standard library with all it's dependencies?

2021-03-27 22:26

阅读:494

At the time of writing, it looks like it‘s by design and there‘s quite some fuss and confusion about it, see logged issue on GitHub.

Moreover, when publishing a NuGet package for project A referencing project B,
B becomes a NuGet dependency in A; B‘s assemby is not included in A‘s NuGet package.

I deal with it by publishing my own NuGet packages.

I only don‘t like it to have a NuGet package for project B if that one is only relevant to be used with/by project A, as it will appear seperately in my NuGet feed.


评论


亲,登录后才可以留言!