Sorry - just to add some clarification to my VB comment. Essentially, the advice not to learn VB first was because nearly everything you can do in VB.net you can also do in C#. There are a number of concepts I think it is important to learn early on, though, even if at a later date you use a language that doesn't implement them. I'm thinking of things like:
[list=]
[*]Static classes
[*]The ternary operator
[*]Case sensitivity - it's tricky and a pain to suddenly have to remember that case matters.
[*]Semi-colon line termination - as above
[/list]
Actually, as I'm writing this list, I think the main thing is that the look and feel of VB is less like a lot of more-modern C-like languages, such as Java, C++, Objective C, PHP, ...
Just little deviations in style more than anything else:
[list=]
[*]Code blocks are limited by curly braces in C#, and START-BlockName - END-BlockName
[*]VB has IF-THEN-ELSE-ENDIF style conditionals; C# has if(){} else {} styled ones
[*]C#'s keywords are more like what I'm used to from other languages
[/list]
Maybe I'm being fickle, and it has been a few years since I've done any real .Net development, and in that time VB does seem to have gained some features (Modules still confuse me, though!
). Either language will do you fine, and both have dot-net at their heart, but personally I would choose to learn a C-style language first, before a "wordier" BASIC-type language.
