>>>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.
>>
>>I think most replies that you will get will be subjective.
>>I think it's true that there are more on-line tutorials / code examples for C# than VB.NET
>>The wikipedia comparison is useful : http://en.wikipedia.org/wiki/Comparison_of_C_Sharp_and_Visual_Basic_.NET
>>
>>The two main reasons I prefer C# :
>>(a) it's case sensitive
>>(b) VB has 'Option Strict Off'' . But it dfesn't matter as long as you are prepared to shoot anyone who sets it that way :-}
>>
>>Can't think of too much that's available in VB.NET but not C#. XML Literals maybe - but I can live without it.....
>>
>>Just my 10c. Oh and I think C# developers get paid more. Not sure where that leads though - maybe go with VB.NET and pay less for programmers :-}
>
>Why do you like case sensitivity? That's not a leading question, nor is it a big issue to me. It just seems like asking for trouble if two variables differ only by case.

TBH, if pushed to rationalize, I'm not sure.
I like being able to use pascal case for types and properties whilst using camel case for private variables, parameter names etc. (this is pretty much in line with the MS naming guideline). I just find it more readable the using a 'm_' or '_' prefix although I accept that these make the context more obvious.
Of course you can't depend on case sensitivity for any public types/properties exposed by an assembly in case it is consumed by a non-case sensitive language.