Version 3.6.1 test release

Release early and often :)

Rocky

Awesome!

Thanks for getting this out early. We are in the middle of some LINQ sorting issues and need to try out the new code for filtering and sorting. We were prepared to wait another 10 days or more for this so it is good that you got this out early.

Joe

At this point ERLB doesn’t have any special LINQ support like BLB.

ERLB is a complex thing to start with, and our support for LINQ continues to evolve – and it too is complex (to say the least). At some point we may provide LINQ support in ERLB as well – though I’m not entirely sure what side-effects we’ll encounter (I suspect they’ll be somewhat nasty).

Rocky

Rocky,

You mentioned
Add support for sorting a BusinessListBase list into a LinqBindingList through a LINQ query.

What about EditableRootListBase? Is there difference in how these listes work regarding LINQ support?

CSLA has several collection types, all of which work with LINQ.

BusinessListBase is intended for editable lists of editable objects, where all changes are saved as a batch. When you do an identity projection against a BLB collection, you get back a LinqBindingList, which is a synchronized view over the original collection. Read Chapter 14 of the Expert C# 2008 Business Objects book for full information about this.

ReadOnlyListBase is intended for read-only lists of read-only objects. LINQ to Objects works fine over an ROLB, and CSLA does no extra work in this case (though the LINQ to CSLA support for indexed queries does work). So you’ll get back a normal IEnumerable<T> from any query.

EditableRootListBase is intended for editable lists of editable root objects, where the list is bound to a datagrid control using in-place editing of the data. The whole point of this collection type is that changes made by the user are committed automatically to the database when the user moves off the row in the grid. So ERLB is designed for a very narrow type of user experience in WPF, Silverlight or Windows Forms. CSLA does no extra work around ERLB, so a LINQ query against it will return an IEnumerable<T>.

The whole reason for a BLB query returning an LBL is the expectation that LINQ will be used to filter/sort an editable list, and that you’ll want to bind the result of the query to your UI so the user can interact with it. I expect the same is true for ERLB – but the complexity of ERLB is quite a bit higher, and so it fell out of scope for the 3.6 release.

Rocky

Thank you.

You intrigued me. Don't want to ask any questions to not ask stupid ones :) But I have a great interest in supporting sorting for all kind of lists for desktop applications. As I found before the only option working for WPF Toolkit DataGrid is using Linq. Which works fine even now with ERLB, the only problem is I have to recreate Linq list (or whatever is the proper name for it) and reassign it to the gird's ItemsSource when items added to or removed from the list. Modification works fine from binding point of view. As our grids are really readonly, we probably do not need that scary stuff you mentioned. Although that's were I may go into stupid comments :)

Oh my! I hope not! :)

Other than a couple minor tweaks, this is pure bug-fix stuff.

Rocky

<Sigh/> Less than three weeks and my new book is already out of date.... ;-)

Isn’t it this one?

http://www.lhotka.net/cslabugs/edit_bug.aspx?id=286

If not, I imagine it is related, so I’ll add the other thread as well so I don’t lose it.

Thanks!

Rocky

Rocky, I don't mean to um ... bug you about this, but I've looked in bug tracker and I don't see the issue that Andreas is reporting. I reported it too, http://forums.lhotka.net/forums/thread/29863.aspx before I realized that he had already done so. This is about BLB raising two ListChanged when a child property changes.

Ross

RockfordLhotka:

I saw the BLB issue reported and added an item in bugtracker. I missed the other one though, and have added an item now as well.