I got some unusual sorting behavior when applying the sort expression twice to the view:

ISortExpression sorter = new SortExpression();
sorter.Add(field1 | SortOperator.Ascending);
sorter.Add(field2 | SortOperator.Ascending);
sorter.Add(field3 | SortOperator.Ascending);
EntityView2<MyEntity> myView = new EntityView2<MyEntity>(myEntityCollection, sorter);
myView.Sorter = sorter;

When I create the view with the SortExpression OR assign it to the view later, it is fine. It is when I apply it (accidentally) using both options that the sorting doesn't appear to work.

I'll leave it up to you if such behavior is undesirable, non-redundant code fixes it

This is using LLBLGen 2.6.8.709 in VS 2008.

Reproduced with three fields. One or two fields is ok. We will look into it. Thanks for reporting that.

Will look into it!

Reproduced. The sorting is completely messed up it seems.

(edit) fixed in next build. The second sort action of a view was always wrong, no matter if you passed 1, 2 or 3 fields, although it might have seemed that it was only wrong with 3 fields. The problem was that it re-used the indides in the collection as the index in the view, which went wrong in the second sort as the order was probably wrong.

Thanks for looking into it and finding it so quickly.