>>Marketing ploy or not - if it is a bona-fide success story - that is all that counts. What does motivation have to do with it?
>
>Bona fide? Here you're implying it is a success story and it couldn't be so if they kept it in VFP. That's nothing more than cheap blah, blah, blah pumped by MS to tell the world "how explendid the .net technology is"!
>
>Fernando


Hold on...where do I say - either explicitly or impliedly that it could not have been a success story if they stuck with VFP when migrating to the web? Likely, we would not have heard about it because MS would have never commissioned a case study.

I find it interesting that with some in the VFP community - .NET gets panned because it is new, untested, immature, etc. etc. Now - some 2+ years down the road, when apps have been written and deployed - .NET still gets panned.

Your post confirms to me that with some, VFP must be promoted at any and all costs. Why? Because it is the tool that you use - and therefore, it must be promoted at the expense of all others.

Personally, I don't think the issue is with case study per se - and the fact that .NET was used. I think the problem is that .NET displaced VFP. Had the case study discussed displacing VB 6 - I don't think there would be the backlash.