Silverlight LinqBindingList

Silverlight LinqBindingList

Old forum URL:

am_fusion posted on Thursday, February 18, 2010

I have done a bit of searching around to see what the status of LinqBindingList is regarding silverlight and can't seem to find much.  Last post I saw indicated that this is not available (yet?) for silverlight.  We have a situation where having this would be nice and I was wondering if there was an update or ETA for its implementation.

RockfordLhotka replied on Thursday, February 18, 2010

This will be done in CSLA 4.

But you should know that LINQ to CSLA is undergoing a rethink in CSLA 4, so it won't work the same. Key points:

In SL the only class will be LinqObservableCollection of course, because there is no BindingList concept in SL.

am_fusion replied on Friday, February 19, 2010

I am not so sure we will have the luxury of upgrading to CSLA 4.0 'soon'.  I assume that, due to the changes in indexing, it will not be straight forward (read relatively painless) to port over to v3.8.x?  

RockfordLhotka replied on Friday, February 19, 2010

There'll actually be quite a few changes going from 3.8 to 4, as the major version number is changing.

If you use indexing there'll be some rework because you'll have to switch to using i4o or something like that. Few people use indexing, as it is such a narrowly useful feature, but if you do use it the impact is there.

Of course CSLA .NET for Silverlight doesn't have indexing either, so that is a non-issue when moving from 3.8 to 4.

Or to put it another way, people using SL will only benefit (in terms of LINQ) when moving from 3.8 to 4. It is .NET code that might employ indexing or synced lists that will be affected.

Once I have the LinqObservableCollection working in CSLA 4, you may be able to back-port it to 3.8. I don't think I'm using any .NET 4 specific capabilities - it isn't like Microsoft has changed the way LINQ or ObservableCollection<T> work in any substantial way from .NET 3.5 to 4.

am_fusion replied on Friday, February 19, 2010

Sweet!!! that is good news.  I am now thinking I will be keeping an eye on trunk and 'back port' the LinqToObservableCollection when I get the time... no rush for you though, we have found a workaround we can use until then.

Copyright (c) Marimer LLC