>Hi all
>
>I know this is a real long shot, but over the last few months discussions seem to be getting extremely tense when it comes to comparing VFP to .Net, a lot of heated arguments tend to erupt from what some people seem to take very personally.
>
>I, myself, would love to have, to hand, some realistic differences between VFP & .Net and where the main strengths/weaknesses lie. I know it's been done before (successfuly? I don't know) and there is probably tons of material out there on this (or is there?) but I feel people need to be informed of why they are chosing a product they are chosing, NOT BASED on arguments generated in this forum, but rather decent laid out differences.
>
>I know you probably think I'm a fool and possibly tempting fate here but I would be very interested, without it getting nasty :-), to hear advice from experts from both sides, and it not to be a result of a stupid argument. I also understand Mr McNeish's book also covers this, but only on an introductory level, IMO.
>
>If anyone thinks it's a bad idea, let me know and I won't kick-start the discussion, otherwise I'll attempt to get things rolling.
>
>Thanks
>Kev

Kevin,
Just a spoonfull of ideas :) I started to work with C# almost a year ago. When someone tries to compare VFP vs .NET I assume main question is how good .NET at data. Well to my personal thought .NET is bad at data. Formerly it was ADO as the engine, now ADO.NET. ADO was like tooth pulling, still it's with ADO.NET, only hurts less.
IMHO if you don't care dog slow winforms, don't care not having a local data engine then VFP is not comparable to .NET.
Probably I still can't do it right, otherwise my poor 650Mhz box is not designed for .NET but VFP, I find it scary to return to IDE to correct a simple error that can't be caught during compilation - well how much it helps to catch errors at compilation through strong typing is another story:)
XML plays a great role in .NET and actually I hate the inventor of XML whomever they are (what a way to define the data - too much redundancy. OTOH talking against XML needs great courage when world is after it:)
Cetin