I'm still working a lot with VFP. I've began to look at .net but I still have a long long log way to go before being really good with it. In the meantime I look at all the stuff they're releasing for .net and I'm a bit scared by what I see.

EF looked really promising but some said it is'nt all it should've been.
LINQ to SQL dead already. Now I read that EF should be the solution in the version 2.

So now we have EF that is not really finished. Like MC Hammer would've said "You can't touch this"
and the days of L2S are over.

So now what are the next good news emerging from MS­?

Perhaps MS should stop developing in-house right now and follow my suggestions.

1. Check what the others are doing.
2. Buy what looks like the best app.
3. Put MS logo on it
4. Sell it at a price the others can't match
5. hope competitors won't be able to last for long
6. Raise prices when competitors get out of the business
7. go to step 1

Oops what was I thinking they already do this.

Hmm looks like there's no way out... unless I'm able to do what my customers need with VFP until they (MS) figure out how to fix the tower of Babel.




>Denis, Google "linq to sql dead"
>
>Behind the semantics, MS is allocating primary focus to the EF. People who tried, liked and began investing in L2S last year are now disadvantaged. The luddites who kept using typed datasets (or untyped datasets) and ADO - or VFP for that matter- are probably better off. QED.
>
>In fairness, some people here had reservations about L2S. KG was unimpressed by some of the queries. Rick Strahl warned that the insiders were saying that the EF would prevail. The glaring deficiency I saw was that the change tracking did not survive passage between tiers unless you rolled your own. So it wasn't perfect. The challenge now is to know how it will be replicated in the EF and when it will be the right time to invest precious company or customer funds without risking obsolescence around the corner. I know that this is more worrying to some people than loss of MS support in 2014.