>Specifically, if you want to create web services without the extra COM layer, you cannot do that in VFP but you can do it in .NET.

THis is really a non-point, since that layer is taken care of by wizards. Exactly the same way .NET handles it, its all underneath.

>From a human resource standpoint, it will be far easier to find .NET developers as opposed to VFP developers.

Maybe in 4 or 5 years. Take a look at the .NET developers today. Ones who know what they're doing are few and far between. Every one's a rookie. Read some of the articles. The huge majority are all plagarized from sub-standard GotDotNet articles.

>And FWIW, the business implications are what normally do and should drive the decision...

Rofl! So, .NET can't run on older hardware, but we shoudl just ignore the tehcnical implications. Examples go on and on, thats just the easiest one. This is some of the worst advice in this thread.