Why?!

Becuase you keep modifying the post that I'm trying to respond to! ;)

At any rate, I agree that there was no intention to annoy or anything.

The issue is a conclusion that can't be fully made after 3 months.

There's the old expression that "nothing happens in contradiction to nature, only to what we know of it". Too many times expressed shortcomings in .NET are more a case of insufficient knowledge or just general inexperience.

.NET is too complicated a technology to learn in 3 months. There is a great deal of knowledge that only comes after a few iterations. I've been writing and speaking on topics like ADO.NET and remoting for over a year - and I'm still coming across new capabilities.

Here's a direct quote: "All factors considered, VFP is a faster design to delivery development platform than .Net for desktop applications" 3 months is not enough to make that conclusion. I'd be a little surprised if anyone who has built applications with both tools would disagree.

IMO, I don't think one is truly any faster a platform for desktop apps than the other. Yes, .NET has a steeper learning curve. But let's make a distinction between the learning curve of a technology, and the capabilities of the technology itself.

He decided to stick with VFP. That's fine. It would be wrong to switch to a technology that he's not comfortable with.
I'm not at all surprised that he decided to stick with VFP - I would have been more skeptical if he felt comfortable enough with .NET after 3 months.

He closed by saying, "Will I put a bread and butter project that pays the rent on .Net/SQL when I am bidding a price competitive contract. Hell No!". Again, fine. This is an open forum, and my point is that some are not only willing to do so, they have and are.

Kevin