References don't necessarily end with ".dll"

Feb 3, 2011 at 10:40 AM

Why doesn't nuget add a reference to an executable file if it's placed in lib/[framework version], whilst it does add references to class libraries from the same folder in the same package?

Why does nuget consider a package with only one executable in the lib folder to be a solution package (which is actually wrong)?

How to remove a solution package (Its not listed in the package references dialog, but its present in the packages folder in the solution)?

Why can I install a solution package again and again in the same project and where should I see that is installed?

Why does nuget cache the responses from the webserver hosting the feed, which is a mess during package development?

Feb 3, 2011 at 12:18 PM
  1. It's a bug. We should detect exe's and dlls, right now we only do the latter.
  2. You have to remove it from the command line. The dialog is project specific (even though it still shows up, we have a bug on this
  3. That's only in the dialog (because of the bug in #2), and you see them in the packages folder or doing Get-Package from the console.
  4. The newest webserver has removed the caching, though for package development why not use a non http feed?
Feb 3, 2011 at 8:24 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.