Hi Jess,

>Aside from shorter learning curve benefit of VFPer moving to VB.Net what else you have in mind are the advantages other than using C#?

The learning curve is definitely an important aspect and since the syntax of VB .NET is more similar to VFP, VFP developers can look at code and understand things faster.

Small things start making a difference once you start using it. Take debugging for example: The Immediate/Command window in the IDE does not support intellisense so if you are using C# and there is a typo (case sensitive), you are pretty much out of luck. Things like With-EndWith don't exist in C#.

It is also a mindset change so when you look at something like:

// C#
for(;;)  
  DoSomething();

it actually maps to a While-EndWhile in VB .NET

// VB .NET
While True
   DoSomething()
End While

Not a very common thing to see this type of code but it is one of the small things to overcome.

Also I had mentioned in one of the earlier thread: (extract)
"VB .NET has something which C# does not have today and we probably will never see it in C#. The Imports statement in VB .NET allows to import namespaces+classes. It is like doing a "SET CLASSLIB to a class in a library". This allows developers to create custom libraries (like the VFPToolkit) and access them as if it were a part of the core language."


Kamal