Hector,

>VB.NET is more suited than C# for the type of applications that you currently build with VFP. In other words, VB.NET is more suited for typical business applications while C# is suited for more system-type of utilities.

I beg to disagree with you here. .Net languages use the same .Net classes in building DB applications. I think the issue here is more on the learning curve of going to another language from VFP perspective and not on the type of application we want to build.

>To me, choosing C# over VB.NET due to the advanced features is like choosing C/C++ over VFP just because C/C++ is closer to the Windows API than VFP.

No. C# is a RAD programming tool just like VB. In fact C# syntax is more concise than VB.

>I've heard people saying "I would much rather use Delphi or C# than VB.NET" and a lot of times this is just based on the "let's hate VB" mentality. That's OK if that is what you want. Just make sure that is *really* what you want.
>Ken Levy gave a nice list of VFP-like features that VB.NET provides and C# does not. Take a look at message #652549

Those are just shallow reasons for good programmers in choosing VB over C#.