>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.
>
>
>Gary.

Honestly, while VB syntax is easier (I agree and started with vb.net myself), I think C# is the better choice for the long run (I agree with the link Viv provided even though the article is 5 years old). It's always been said that it's perfectly fine to choose either - it's a personal preference. However, to me (IMHO I stress) it seems there are far more resources available on the web for C# code examples and more jobs available. I've been happy with C# and the learning curve is not that much more than vb.net

Update: I can tell you this; my experience has been that the developers I've worked with who learned C# and were not vb.net developers who switched to C# just for the job do much better coding in the beginning in a multi-tier strict design pattern environment...Some of the vb.net developers need their hands held a lot (they cannot even read VFP code) - however; once they are familiar with the design pattern and the C# syntax, they do much better and are more on par with the other developers. Of all of the C# developers I've worked with so far - very few have had a problem reading VFP code (for those apps that get rewritten). I'm speaking of a personal, not just professional experience though. I get a lot of requests from other C# or VB.net developers outside of my job to help with interpretating vfp code so they can rewrite it in C#.