VFPs' RAD capabilities and data centric solutions currently stand on a much higher level.Walter, there's a point that's being seriously missed. I don't dispute (and have never disputed) that VFP has several 'out of the box' capabilities that .NET doesn't have 'out of the box'. (And vice-versa). That's not the point in evaluating the capabilities of a product.
VFP is generally a 'higher-level' tool than .NET, so that's almost to be expected. But .NET also has a rich framework that allows someone to build the same type of solutions that are built in VFP. Yes, you have to write some code (something you recently expressed a disdain for doing, most recently with a 'yuck' reaction). Last time I checked, our general professional responsibilities did include writing some code now and then. ;)
It's the old philosophy about the fiddler and the fiddle.
I'll grant you that when I first looked at .NET in 2001, my reactions were not totally unlike yours. But I was looking at it from the wrong angle, partly because I had fallen into the 'Fox-box', and (to use JVP's prior post), looking at things far too tactically and not enough strategically.
Kevin