>>>>>Hi All,
>>>>>
>>>>>I'm a VFPer doing some gradual poking and prodding into the .NET world regarding data access. I've found some information on the web about the Entity Framework and I'm hesitant to learn more about it because of the negative stuff that I've seen and heard.
>>>>>
>>>>>Has it improved since the no-confidence vote over a year ago?
>>>>>
>>>>>Does anyone here have any experience with the Entity Framework and if so, what are your thoughts about it?
>>>>>
>>>>>What alternatives would you recommend and why?
>>>>>
>>>>>TIA,
>>>>>Mike
>>>>
>>>>Mike,
>>>>It should be a wrong interpretation of what you read/seen/heard I think. EF is all well and getting much better. I would recommend EF. The one negative stuff might be it is slower than L2S. In that case, provided I don't need newest SQL features I simply use L2S.
>>>>Cetin
>>>
>>>However, the scuttlebutt is that L2S is going to be deprecated.
>>
>>Yes, it wouldn't be worked on. In its current state it is working and as I said if "I don't need newest SQL features" it fits the bill. That news however made many developers Linq itself was depreceated:)
>>Cetin
>
>Shame, because one of the things I really liked about L2S is the query in memory feature. It's the closest thing to the practice in VFP of querying from result sets.
Tracy,
I think I didn't understand:) With EF you can do too and may be more. L2S and L2E are very similar. My favorite though is when I can make them local (ie: AsEnumerable()).
PS: Wish I can complete last "Linq operators" entry this year:) - and probably then do extensive sampling on CRUD like operations.
PS: LinqPad supports EF and esql too.
Cetin