Hi Kevin !
When I looked at C# I fall in love with it from first sight, but I am afraid that jumping in C# hurts more my productivity than jumping in VB.NET.
(I make financial application for end user not tools and components for developers)
I have three reasons:
First reason: case sensivity - it looks that it can drive mad a VFP developer.
Second reason: intellisence - it seems that in VB.NET it is made more comfortable than in C#.
Third reason (main reason): If in a future I will develop/maintain several projects some in VFP some in NET, it seems that it will be easier constantly switching my mind between VFP and VB.NET than between VFP and C# -just because many VFP language are VB like not C# like.
Am I wrong ?


>
>Based on my experience (teaching LOTS of VFP developers C#), I have to disagree with this statement. I have found that VFP developers--even those who have never used anything but VFP--learn C# very easily. Although C# has some OOP and language advancements not available in VFP, many of the concepts are the same, and it boils down to learning the syntax of the language...and C# has very clear, consistent syntax that can be learned very quickly.
>
>Developers who are unfamiliar with advanced programming concepts would have an equally difficult time learning these in VFP, C#, VB .NET or any other programming language.
>
>Regards,


>>My main point is that for many VFP coders VFP is the ONLY language they know. With no prior CS training or experience the Dark Side of the Moon is all they know. Stepping from VFP to a language similar to C++ when all you've ever known is VFP will be a programming-life-ending experience for all but the best of them.