>>
>Why anyone would want to give them the chance to do it again is beyond me. There are things I can do with VFP that I could never do with .NET; and after investing so many years learning it, why should I start over with .NET just because MS says it's what I should use.
>
>I sure and the heck won't invest years of development time trying to convert apps that are working perfectly just so I can say they are written in .NET. In some circles, that would be a negative.

Rewiting to NET became more then technology issue apparently;

I have heard here that you can even get sued by some offended client for 'misguiding' them into purchasing your VFP application
nowadays. I always had my doubts about corporate intelligence, but this goes way beyond lowest 'credits' I could possibly give them.
But then again strange things happens in corporate America all the time, so anything is possible I guess.

I wander if anybody got sued or at least lost their corporate IT jobs, because of failed premature conversion to NET (costing few mil or more), that has been started back in 2001, based on nothing more but guru's ramblings, technology previews,
writings on the walls and that kind of things. I have heard that many of those went really really bad.

So, how come corporate lawyers did not get so vigorous in these cases ?