For example: $orderby=ByteArrayProperty, CollectionProperty, ComplexTypeProperty, NavigationProperty.
We should report proper error for such case instead of closing the connection.
Comments: This is Won't Fix'ed. The real issue here is that the self host server is not sending back the right error message to the client. We will hopefully fix this issue in vNext. As for possible workarounds, we could detect that the provider is Linq to objects and require that OrderBys happen on IComparable types, but that would be specific to the Linq to objects provider and would not apply to custom query providers.
We should report proper error for such case instead of closing the connection.
Comments: This is Won't Fix'ed. The real issue here is that the self host server is not sending back the right error message to the client. We will hopefully fix this issue in vNext. As for possible workarounds, we could detect that the provider is Linq to objects and require that OrderBys happen on IComparable types, but that would be specific to the Linq to objects provider and would not apply to custom query providers.