This project is read-only.


Nuget package Manager sort do not successful


Rerpo Steps:
  1. Create a MVC project , then open nuget package manager.
  2. tpye "" in online search textbox. Then search.
  3. Click sort by :"Name:Ascending"
Issue: the list item not sort correctly , such as “Json.NET” should on the top of “JSON-RPC.NET Core” according compare their ASCII value. The issue is found by automation test by ) ListItem's name.
see attachment.

file attachments

Closed Feb 16, 2013 at 1:29 AM by dotnetjunky


danliu wrote Jan 18, 2013 at 7:55 PM

Changing the Impact to medium, as this is affecting our automation results.

tilovell wrote Jan 22, 2013 at 6:31 PM

I think this is by design. In fact, the old behavior was a bug. English dictionaries do not sort by ASCII values, they sort case-insensitively. NuGet's alphabetical sort should work the same as a dictionary.

JeffHandley wrote Jan 22, 2013 at 7:36 PM

We should be sorting with:
  • Invariant Culture
  • Ignore Case
It looks like we are. The "-" comes before the "." in the ASCII chart, so the current results look like they are correct.

Closing as By Design.

** Closed by JeffHandley 01/22/2013 11:36AM

ChengBinlin wrote Jan 23, 2013 at 4:39 AM

Thanks for the commnets, but still have a sight issue oninstalled table, such as package name "AB" with"ABC"
For example as attment "MVC4PackageSort.png" and "MVC4PackageSort2.png".
"DotNetOpenAuth OAuth 1.0(a)" with "DotNetOpenAuth OAuth 1.0(a) Consumer" sort result on "installed package" tab is different with "online serarch result" tab, both under Ascending.
Note this is MVC4 internet project template.

ChengBinlin wrote Jan 23, 2013 at 4:40 AM

add "MVC4PackageSort2.png"

ChengBinlin wrote Jan 23, 2013 at 4:41 AM

See above comment, still have issue on installed tab

JeffHandley wrote Jan 24, 2013 at 8:12 PM

The installed tab does look wrong. Moving to 2.3.

JeffHandley wrote Feb 14, 2013 at 6:49 AM

Clearing my name off Assigned so that someone else can pick it up.

dotnetjunky wrote Feb 16, 2013 at 1:29 AM

This is a minor issue but not trivial to fix. We don't think it warrants a fix.