I'm wondering what the motivation was to not allow child collections to be bindable at design time:
[
Browsable(false)]
[Bindable(false)]
Basically, I have a Customers object, which has a Zero-Many association to CustomerContactInfo. I wanted to use a BindingSource set to my customer object, and then another BindingSource for the associated contact info. However, this isn't allowed without removing those attributes from the generated classes. If this behavior is on purpose, is it because of performance considerations? Otherwise, what's the deal?
BTW - great framework. I'm switching an application that was using Gentle.NET to EntitySpaces, and I have to say, the performance is SIGNIFICANTLY better (loading a grid of 8000 records takes a second, compared to about 30-40 secs). It's almost as fast as loading/manipulating ADO.NET datatables, and it definitely performs better than many other entity frameworks out there!