Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Package .nuspec is missing the <developmentDependency> flag
See original GitHub issueJust realized that after installing the PrivateAssets="all" is missing in the PackageReference node.
I have added PrivateAssets="all" manually for all weavers where this was missing, and it always worked fine, so looks like #362 is outdated and only relates to use of package.config, which IMO can be considered as obsolete.
There should be a property <DevelopmentDependency>true</DevelopmentDependency> in the project, like in Fody
@SimonCropp I did not check other weavers yet, but I guess this is missing in others, too. Maybe this should be added as a default to the FodyPackaging.props?
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes, agree, I will try to do something next weekend.
Unfortunately if just one project in the chain of dependencies forgets to add the
PrivateAssets="all", the final output will have the weavers attribute-assembly marked as a deployment dependency 😞