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 metadata to unlist the package by default
See original GitHub issueSome packages are there merely to serve as common dependencies for several other packages, and aren’t useful to be listed for public consumption (because there is no public API in those packages, for example).
It would be great if there were a .nuspec xml element, like <DependencyOnly>true</> or <Unlisted>true</> that would hide it from the public listen to avoid cluttering up the packages list.
See discussion here: http://nuget.codeplex.com/discussions/291138
Issue Analytics
- State:
- Created 12 years ago
- Comments:7 (4 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
Even so, it seems like a
<DependencyOnly>metadata in the nuspec file wouldn’t be misplaced. It is an aspect of several of my packages (not the way I upload them) that they have no public API and should never be added directly.Is there a possibility of getting this in? Nuspec metadata works much better than a command line option in my case (AppVeyor).