>>>I (and a colleague) are finally embarking on the move to .Net.
>>>
>>>We have decided to follow the MCTS -> MCPD paths and gradually get qualified (my first ever qualification in IT since I am 100% self taught!)
>>>
>>>But we can't decide if we should go VB.Net or C#.Net, We are a vertical market developer, and currently use VFP9 desktop apps with VFP back end and an ASP.Net (VB Script) web interface.
>>>
>>>I know VB syntax would be easier to learn and I did a little VB years ago and the web stuff is currently VB, but are we then just learning another dying language? (don't jump on me that VFP's not dead - I LOVE the Fox and will use it as long as possible, but it is dying). Is C# worth the steeper initial learning curve and will it's very difference stop us getting the two syntax confused?
>>>
>>>Any thoughts welcome.
>>
>>I'd go with the one you are most comfortable with - which sounds like VB in this case.
>>From a language POV the differences between VB and C# are getting less with each version.
>>Interesting wider perspective here tho (that may raise a few hackles :-} ) :
>>http://www.codeproject.com/kb/dotnet/CSharpVersusVB.aspx
>>
>>Snip:
>>
>>1.80% of C# programmers are good, while 80% of VB programmers are not good. This is not to say that everyone who programs in VB is less skilled than everyone who programs in C#. This is to say that:
>>a.the VB syntax and semantics is designed to attract less skilled programmers and, in combination with other factors examined above, this has created a culture that is populated with less skilled programmers.
>>b.and because VB syntax and semantics make it more difficult to avoid common programming errors and hence to program well.
>
>Do you believe this or are you just snipping? I have no idea about the breakdown but since by my own estimate 80% of all "programmers" are poorly skilled and even less skilled in software design as a function of business requirements gathering it seems a moot issue for which language an individual should choose.
>
>Point b. just seems silly. Can you give examples of how VB .net makes it "more difficult to avoid common programming errors and hence to program well."
>
>I think everyone should be comfortable reading either and then do their own code in whatever seems more instinctive. This would be a good argument for every person beginning .net to go through at least rudimentary syntax learning in both, then decide.

I agree completely.

C# seems to be what clients think is better (like VB vs VFP). that is simply the truth in the market.

VB.NET works fine, and the IDE doesn't fight you constantly which is why I prefer VB.NET. I can do C# in a pinch, and if I want I can write really complicated code and make it as obtuse as possible, but I prefer not to. I prefer simple and direct (which usually translates to easier to debug and maintain).

I'll do C# if a client requires it. If it is my choice, VB.NET is my pick because I can get more done faster.

Yeah - go ahead and flame.