Nuget GUI does not detect updates from custom package source

Jan 4, 2011 at 7:27 PM

I refer to this issue:

The cause of the issue is that the Updates tab only show updates from the Active package source. The Active source is selected from the Console, (and used to be from the Options dialog). This is unintuitive behavior; nobody would be able to guess that. We have 2 options to fix it:

  • Under the Updates tab, provide one tree node per package source. This is consistent with the Online tab.
  • Aggregate all updates from all package sources under the current All node.
  • Or maybe both of the above?


Jan 4, 2011 at 9:01 PM

I like the last option.

If I installed a package from one feed, I may want to know if that’s the feed offering an update. If we only offered Aggregate, then we could run into a case where you installed from one feed, but another feed provided the update. In theory this shouldn’t be a problem, but users might want to be able to determine where the update is coming from.


Jan 4, 2011 at 9:49 PM
Edited Jan 4, 2011 at 9:50 PM

I prefer an aggregate from all package sources.  My only concern is the same that Phil brought up.  If I have a private package source with a custom build of say NHibernate, what happens when both the official feed and my feed have updates for NHibernate? 

Jan 4, 2011 at 9:55 PM
jgeurts wrote:

what happens when both the official feed and my feed have updates for NHibernate? 

 The current behavior of the dialog is that we display the latest version. If they both have the same version, then it's undeterministic :) If you want to choose the specific update, you select the specific source.

Jan 5, 2011 at 12:37 AM

I agree with the idea of having both, that way I can limit just to a certain feed. This scenario may come more into play if I have a feed with beta packages I want to ignore when updating or scenarios where I care about which source I want updates from (already mentioned).

"Be passionate in all you do"