>I heard rumors that the whole 'linq to sql dead' issue came about due to a power struggle internally in MSFT. The entity framework won out in that one supposedly. I've heard both pros and cons from both sides. It will be interesting to see if there is enough usage out there and rucus created by the killing off of it to stop it from happening...
>
>Deja vu...

Yeah, Whenever I hear/see that 'Writing on the wall...' thing, I get urge to immediately rewrite all applications I have ever written... ;0)


>
>:o)
>
>>Not wanting to take sides, but it's worth googling "linq to sql dead." L2S was introduced last year and despite being scoffed at by some MVPs it has gained quite a following amongst data developers, as you can see from all the dismayed comments at the suggestion that it is being deprecated.
>>
>>My point: before picking any new scenario you need to consider whether you are jumping out of the frying pan into the fire- IOW whether the selected technology will in fact give you greater longevity than VFP.
>>
>>This isn't a pure MS phenomenon, either: you can see it in lots of places meaning that "longevity" needs to be right up there on the checklist if you are considering any sort of change.
>>
>>FWIW I don't think the prospects for L2S are anywhere near as dire as some have interpreted, but it's a timely example. Certainly it allowed me to throw together some data stuff that would not have been economic with the Entity Framework as it was at the time.
>>
>>And sorry for seeming to direct this at you; yours was just the most recent post. ;-)