>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 like a lot of VFP people moving to .NET I found VB more comfortable. Since I was adopting Strataframe as my framework and that was tilted toward VB that worked for a while. After a while I found I had to have a working knowledge of C# to understand code samples and tutorials that were very predominantly C#. Then I started Pluralsight training, entity framework and working with Devforce and getting a lot of information from stackoverflow and that was all C# so I just switched and have never looked back except to support my old VB apps.
My suggestion is start with C#. You won't find a lot of necessity to also know VB, where if you go with VB you will basically have to learn both.
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
