>>but I think it is a dis-service to try and paint it is the "right .NET tool" for VFP developers - and that's what I see happening.
>
>I think the majority of people you refer to have simply pointed out that VB.net has features and similarities to VFP over and above say C#. Given that the deal is really learning the framework which will be a fair task in itself, it kind of makes sense to inform people who can't program in VB or C# that "before you waste a lot of time, you might like to know than on balance, VB.net will probably come a little easier to you, a VFP developer" (curly brackets, semi-colons, case sensitivity, with-endwith etc., etc.,).
>
>They might give different advice to a C/C++ or Java developer. If we have to learn a fairly large framework with a 1000+ classes, why make the job harder by learning one language that may make less sense to a VFP developer than another?
>
>Can't see what your beef is here.

I have no 'beef' -