That is eerily close to my own POV. When I decided to put my efforts into C# it was strongly influenced by ex-VFP developers I respect going in that direction.

>Faced with that choice a few years ago, I looked at both and chose C# simply because some .NET developers whose judgement I respected told me that the languages were equally powerful, but the C# rates were higher and that there was more demand for C#.
>
>That made the decision easy!
>
>That selfish motive aside-
>I think I made the right call for this practical reason:
>i have no statistical data to support this, but it seems to me that when I search for answers to a .NET problem, more solutions use C# than VB and that's a huge benefit when I'm struggling with a problem.
>
>Here's an interesting side benefit that popped up recently- when you learn C#, you're learning a variant of C.
>At least to this aging VFP developer, the C syntax was really wierd at first and it took quite a bit of effort to master.
>Recently I needed to learn Javascript, another variant of C whose syntax is almost identical to C#'s, and I was pleased to see that my C# knowledge made it a lot easier than it would have been without it.
>
>
>
>>>We are considering adopting .Net as a development environment and we were wondering whether we should go CSharp or VBNet.
>
>We are "leaving" VFP and have extensively used vba in access and excel. We did do some java, c, but not as extensively, so "naturally" we would go VB.Net.
>
>Having done some vbnet, I get the feeling that .net is rather focused on CSharp, and "also" supports VBNet. Is that just an impression?
>
>Are there other criteria of choice that affect this decision?
>
>Thanks for any consideration you might want to share with us.