>
True, but I didn't see any data on how long it took them to do it using VFP to start with (as mentioned in a previous message).
>

Not sure it matters as it would be comparing apples to oranges. The VFP app was not a web-based app. The relevant number is that in 18 months, not only was a new tool learned - the app was completely re-written - with a completely different paradigm.

It also shows that it was not per se wrong to be an early adopter of .NET


>
I get the point though. M$ needs more of our dough. Cough it up... since if you don't, we will eventually put you out of business.
>

MS's primary goal is to have a positive EPS # that meets/exceeds analysts' forecast. A major part of the strategy is to come up with new products and to persuade us - the consumer - that we need those new products. Given that .NET is at the nexus of so much at MS - it is hardly a surprise that MS is making the push to get developers into .NET. Albeit a gentle push - it is a push nonetheless.

My guess is that in the weeks and months to come - we will see many of these case studies. I am waiting for the one that converts a VFP desktop app to a .NET desktop app.