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

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

回答1

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.

 

回答2

测试发现,这个是靠谱的

Try:

dotnet publish

All the dependent libraries should be copied to the publish output folder.

 

 

 

作者:Chuck Lu    GitHub    
posted @   ChuckLu  阅读(211)  评论(0编辑  收藏  举报
编辑推荐:
· 记一次.NET内存居高不下排查解决与启示
· 探究高空视频全景AR技术的实现原理
· 理解Rust引用及其生命周期标识(上)
· 浏览器原生「磁吸」效果!Anchor Positioning 锚点定位神器解析
· 没有源码,如何修改代码逻辑?
阅读排行:
· 全程不用写代码,我用AI程序员写了一个飞机大战
· MongoDB 8.0这个新功能碉堡了,比商业数据库还牛
· 记一次.NET内存居高不下排查解决与启示
· DeepSeek 开源周回顾「GitHub 热点速览」
· 白话解读 Dapr 1.15:你的「微服务管家」又秀新绝活了
历史上的今天:
2019-04-03 Why there is two completely different version of Reverse for List and IEnumerable?
2019-04-03 在Jenkins中集成Sonarqube
2019-04-03 如何查看sonarqube的版本 how to check the version of sonarqube
2018-04-03 outlook创建收信规则,将收到的所有邮件,转发到qq邮箱,然后删除
2018-04-03 everything的使用
2018-04-03 log4net preserveLogFileNameExtension 和 watch
点击右上角即可分享
微信分享提示