Hello there,
I would like to know when you will have complete compatibility with the Entity Framework (EF)?
I have struck a problem where I have a master / detail grid, and in the detail grid one of the columns is another entity (effectively a lookup table) against which I would like to have a combo-box. The problem is that in the detail entity, EF generates the column that has the associated lookup table as a class, not a scalar Id. And as a result I wasn't able to wire up a combo-box that could write back to that column.
I was told by support that this was due to EF being relatively new and that complete compatibility would become available in future versions. Can you give any idea of if/when this would be done.
This is a problem for me, as I am designing the architecture of a new application. I want to make sure the Data Access Layer (DAL) is compatible with the xCeed datagrid, as grids will be used heavily in the application.
Effectively I have gone down this route :
1. Created and tested a DAL using "Linq to Sql" (L2S). This works nicely except that L2S doesn't implement change notifications on deletes and hence when an item is deleted from the datasource feeding a detail grid, the detail grid doesn't refresh.
2. As a result, I created and tested a DAL using the "Entity Framework". This solved the delete notification problem, however as EF generates FK items as classes not Id's, I was unable to wire up combo-boxes and customer cell editors.
I know that I could write my own ORM classes that implement change notifications properly, etc etc, but I am really trying to avoid such a large boilerplate / plumbing coding exercise when EF and L2S are very close to the mark and are suitable for all my other requirements.