>>>Noone with more than beginners experience in either platform can seriously suggest otherwise.
>This statement, however is the type of comment I would expect from the beginners in our field. I did not expect it from someone with experience. It is a put down to all who may disagree and should not have been stated.
>
>What I intended to say was "Noone with more than beginners experience in BOTH platforms can seriously suggest otherwise".
>
>This not meant to be insulting but it is meant to drive home a point. I can appreciate people wanting to stay in their comforts zones and work with technologies that they are more familiar with. There is nothing wrong with that. When the argument shifts from personal preference to a debate on which is platform is better platform is when I start taking exception. There just isn't a real competition there.

I have much more than beginners experience in VFP, C#, VB.NET, ASP.NET, and CF.NET (using VS2003, 2005, and 2008), and I seriously suggest otherwise.

If I need to do something in a hurry, I do it in VFP because I can develop a windows app in VFP far faster than I can in .NET. If data is involved, the development time skews dramatically further over towards VFP (I only use SQL Server data).

C# is a very clean OOP language. I do like it. The .NET classes give it great capability. It also takes longer to do most anything in it unless it is simply a .NET method call.

I do like a lot of the features in the VS IDE. Intellisense in particular is wonderful. If they were available for VFP that would be nice IF they actually responded reasonably quickly.

I work with .NET because that seems to be the current way the industry wants me to develop, and most of that now is ASP.NET (using VB or C# depending on client wishes). If VFP could natively do ASP.NET applications (without hacking ASP capabilities in after the fact) I'd still be doing new development with it.