Accepted answer

why is orderedenumerable<string, string> not available

because it is an "internal" impementation of the interface. there is no reason why it should be available or documented. with linq you should program against interfaces (ienumerable<>, iorderedenumerable<>, iqueryable<>...)

if you take a look, all the linq methods return an internal class that derives from one of those interfaces, and often they can return instances of multiple different classes, depending on the input. for example the can return a new selectlistiterator<tsource, tresult> or a selectilistiterator<tsource, tresult> or a new selectipartitioniterator<tsource, tresult> or various other classes, depending on the type of the ienumerable<> input.

Related Query