I think your analysis is spot on. If your a C/C++/Java developer, you will be right at home with C#. Still, I would encourage those folks to still look at VB. Although, I could see where those folks could have a harder transition. i.e., I think it is easier to go from VB to C as opposed to C to VB. The transition from VFP to VB and vice versa is a slam dunk because they are 80% the same language.

VB did not gain the popularity it did by being a crap language. Like everything else, it has its probloems. Still, it won the war and lived to see a new day! < bg >...



>>On another front, I would caution against not considering VB. Kevin is prejudiced toward C#. Not to take anything away from C#, there is nothing wrong with VB .NET. Personally, as a Fox developer, I think you will like VB more.
>
>Not having ever done any C programming, I agree with you. In the last year and a half, I taught myself VB6, grudgingly at first - the coming to really appreciate what VB developers like about the product. As much as I love working with VFP - the more I work with VB-SQL - I have to say it is a pretty darned good combo.
>
>With my background using VFP (and VB recently), I find the transition to VB.NET rather easy. I am by no means an expert, but I am able to pick up the langauge rather painlessly.
>
>Probably anyone that has done C, C++, Java programming in the past will lean towards C#.